Skip to content

v0.31.0 — per-project filter

Choose a tag to compare

@OneStepAt4time OneStepAt4time released this 27 May 16:29
· 16 commits to main since this release

Highlights

Phase-4 of the CCMeter parity push. Click a project name on the Projects
grid → the entire Metrics tab drills into that single project: KPIs,
4-up heatmaps, period-over-period deltas — all filtered. An amber banner
at the top shows the active filter with a ✕ button to clear it.

The filter persists in localStorage (polaris.projectFilter) so a
reload preserves the drill-down. Per-browser-local — same convention as
the starred set in v0.30.0.

API

GET /v1/metrics?range=30d&project=D--aegis   ← new
GET /v1/heatmap?days=180&metric=cost&project=D--aegis   ← new

Behaviour

  • Unfiltered requests keep the v0.24.0 SQL fast-path (no perf regression).
  • Filtered requests use a JS-side slow path: getEventsInRange →
    filter by projectKey() → per-model rollup. Acceptable cost: drill-
    down is an explicit user action, not the hot path.
  • All 4 heatmaps respect the same filter.

Image

docker pull ghcr.io/onestepat4time/polaris:0.31.0
docker pull ghcr.io/onestepat4time/polaris:latest

What's changed

  • feat(metrics): per-project filter (?project=X) (#82)

Full changelog: v0.30.0...v0.31.0