Files
ottyl/webapp
Hugh KaznowskiandClaude Sonnet 5 10753cc9f8 Wire FilterBar to server-side filter query language (ticket 016)
Send the raw filter string to GET /api/logs and GET /api/timeline
instead of doing a naive client-side substring match, surface the
API's 400 parse error inline under the FilterBar input, and drop the
now-dead visibleLogs client-side filtering in App.tsx.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XFUNZwCvz3kcod3352ZR2o
2026-09-05 13:18:11 +01:00
..
2026-09-05 12:23:46 +01:00
2026-09-05 12:23:46 +01:00
2026-09-05 12:23:46 +01:00
2026-09-05 12:23:46 +01:00
2026-09-05 12:23:46 +01:00
2026-09-05 12:23:46 +01:00
2026-09-05 12:23:46 +01:00
2026-09-05 12:23:46 +01:00
2026-09-05 12:23:46 +01:00
2026-09-05 12:23:46 +01:00
2026-09-05 12:23:46 +01:00

React + TypeScript + Vite

This template provides a minimal setup to get React working in Vite with HMR and some Oxlint rules.

Currently, two official plugins are available:

React Compiler

The React Compiler is not enabled on this template because of its impact on dev & build performances. To add it, see this documentation.

Expanding the Oxlint configuration

If you are developing a production application, we recommend enabling type-aware lint rules by installing oxlint-tsgolint and editing .oxlintrc.json:

{
  "$schema": "./node_modules/oxlint/configuration_schema.json",
  "plugins": ["react", "typescript", "oxc"],
  "options": {
    "typeAware": true
  },
  "rules": {
    "react/rules-of-hooks": "error",
    "react/only-export-components": ["warn", { "allowConstantExport": true }]
  }
}

See the Oxlint rules documentation for the full list of rules and categories.