Bhargav
a7cbf9cfdd
The span "View Logs" button called loadCorrelation() without awaiting it and then passed correlationProps straight to navigateToCorrelatedLogs. When nothing was correlated that value was null, so the composable threw on correlationProps.logStreams and the user saw nothing happen. The tree-view "View Logs" handler had the same gap, silently returning instead. Await the lookup and only navigate when at least one log stream came back; otherwise toast. A failed lookup reports its own reason, while a lookup that succeeded with nothing correlated gets the plain "no correlated logs" wording — correlationFailed tells the two apart, since correlationError is set in both cases. Also tighten the correlation check to require a non-empty logStreams array, so an empty result no longer navigates to Logs with an empty query. The two sidebar specs asserting the old fallback to navigateToLogs were already failing on this branch; they now cover the toast instead.
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