mirror of
https://github.com/openobserve/openobserve.git
synced 2026-11-04 08:09:27 +00:00
Omkar Kesarkhane
d2c60a9ab6
### **PR Type** Bug fix #8727 ___ ### **Description** - Persist histogram results using ref - Replace array ops with ref access - Fix skeleton resets across code paths - Minor formatting and safety tweaks ___ ### Diagram Walkthrough ```mermaid flowchart LR state["searchState.ts: histogramResults ref"] -- "exposed via searchState()" --> stream["useSearchStream.ts: consume .value"] state -- "mapped via .value" --> hist["useHistogram.ts: build mapped data"] stream -- "reset/push via .value" --> hist ``` <details> <summary><h3> File Walkthrough</h3></summary> <table><thead><tr><th></th><th align="left">Relevant files</th></tr></thead><tbody><tr><td><strong>Bug fix</strong></td><td><table> <tr> <td> <details> <summary><strong>searchState.ts</strong><dd><code>Make histogramResults reactive with ref</code> </dd></summary> <hr> web/src/composables/useLogs/searchState.ts <ul><li>Convert <code>histogramResults</code> to <code>ref([])</code><br> <li> Export reactive <code>histogramResults</code> via state</ul> </details> </td> <td><a href="https://github.com/openobserve/openobserve/pull/8651/files#diff-c0ac4f131ad64edd2ed811e183bb570be2f38d58c9ed958d093457a51280ec34">+1/-1</a> </td> </tr> <tr> <td> <details> <summary><strong>useHistogram.ts</strong><dd><code>Use ref-based histogram results in histogram flow</code> </dd></summary> <hr> web/src/composables/useLogs/useHistogram.ts <ul><li>Use <code>histogramResults.value</code> for mapping<br> <li> Reset <code>histogramResults.value</code> in skeleton<br> <li> Push zeros into <code>histogramResults.value</code></ul> </details> </td> <td><a href="https://github.com/openobserve/openobserve/pull/8651/files#diff-4d467d6778569f239f96f3af9ec30214aa8b029892bf40a0aa038dfbb73eca6e">+5/-5</a> </td> </tr> <tr> <td> <details> <summary><strong>useSearchStream.ts</strong><dd><code>Stream logic uses shared ref for histogram results</code> </dd></summary> <hr> web/src/composables/useLogs/useSearchStream.ts <ul><li>Remove local <code>histogramResults</code> array<br> <li> Inject and use state <code>histogramResults</code><br> <li> Replace resets/pushes with <code>.value</code> usage<br> <li> Minor formatting and interval check tweak</ul> </details> </td> <td><a href="https://github.com/openobserve/openobserve/pull/8651/files#diff-0b7e910195d1ec4b1301973bd2f4193e1e23442103f69a9fbd189d3f78547014">+46/-27</a> </td> </tr> </table></td></tr></tr></tbody></table> </details> ___
web
This template should help get you started developing with Vue 3 in Vite.
Recommended IDE Setup
VSCode + Volar (and disable Vetur) + TypeScript Vue Plugin (Volar).
Type Support for .vue Imports in TS
TypeScript cannot handle type information for .vue imports by default, so we replace the tsc CLI with vue-tsc for type checking. In editors, we need TypeScript Vue Plugin (Volar) to make the TypeScript language service aware of .vue types.
If the standalone TypeScript plugin doesn't feel fast enough to you, Volar has also implemented a Take Over Mode that is more performant. You can enable it by the following steps:
- Disable the built-in TypeScript Extension
- Run
Extensions: Show Built-in Extensionsfrom VSCode's command palette - Find
TypeScript and JavaScript Language Features, right click and selectDisable (Workspace)
- Run
- Reload the VSCode window by running
Developer: Reload Windowfrom the command palette.
Customize configuration
See Vite Configuration Reference.
Project Setup
npm install
Compile and Hot-Reload for Development
For stand-alone UI development environment, create .env file and which contains below environment variable
VITE_OPENOBSERVE_ENDPOINT=http://localhost:5080/
npm run dev
Type-Check, Compile and Minify for Production
npm run build
Run Unit Tests with Vitest
npm run test:unit
Run End-to-End Tests with Cypress
npm run test:e2e:dev
This runs the end-to-end tests against the Vite development server. It is much faster than the production build.
But it's still recommended to test the production build with test:e2e before deploying (e.g. in CI environments):
npm run build
npm run test:e2e
Lint with ESLint
npm run lint