Files
openobserve/web
Omkar Kesarkhane 237fbca3af fix: Synthetic check runs table sorting issue (#13477)
## What changed
This PR makes the Synthetics runs table sortable (with a default sort by
last-run, newest first) on all columns, using raw underlying values
(e.g. `durationMs`, `statusRank`, `locationName`) instead of the
formatted display strings the cells render. It also removes a
`tableFilterKey`-based force re-render hack and an inline error-badge
cell/`filterByError` helper that duplicated existing
`filterByErrorPattern` filtering. Separately, it fixes a loading-state
flash in `RunDetail.vue`/`ProtocolRunSummary.vue`: `MonitorResults.vue`
now passes a resolved `overrideMonitorType` down to `RunDetail`,
`RunDetail` seeds `monitorType` from that override in drawer mode to
skip a redundant fetch, and `loadRun()` now sets
`synthetics.loading.value = true` synchronously so the skeleton shows
instead of an empty/wrong-branch UI while monitor type resolves. A new
`ProtocolRunSummarySkeleton.vue` component replaces a generic
`OSkeleton` block to mirror the actual result-card layout. The runs
query limit in `useSyntheticResults.ts` was bumped from 500 to 1000, and
the runs page size default is kept at 10.

## Why
Reviewing `MonitorRuns.vue`'s pagination, default sort, and column
sorting surfaced that columns weren't sortable and had no default sort,
and that sorting on formatted values would produce incorrect ordering
(e.g. "900ms" sorting after "1.2s", or status ordering depending on
locale). Separately, the session's testing turned up a UI flash where
`RunDetail`/`ProtocolRunSummary` briefly rendered the wrong branch
(empty state or "browser" default) before `fetchCheck()`/monitor-type
resolution completed.
2026-07-27 16:04:39 +05:30
..
2025-12-04 13:58:09 +05:30
2026-05-28 11:00:49 +00:00
…
…
2024-04-03 12:49:25 +05:30

web

This template should help get you started developing with Vue 3 in Vite.

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:

  1. Disable the built-in TypeScript Extension
    1. Run Extensions: Show Built-in Extensions from VSCode's command palette
    2. Find TypeScript and JavaScript Language Features, right click and select Disable (Workspace)
  2. Reload the VSCode window by running Developer: Reload Window from 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