c0bb6f4fc7
CRUD increment 3/6. Full delete path lands end-to-end.
Backend (homecore-api):
rest.rs +18 LOC — new `delete_state` handler. Idempotent (matches HA's
removal semantics): returns 204 No Content whether the entity existed
or not. 4xx only for malformed entity_id or auth failure.
app.rs +6 LOC — adds `.delete(rest::delete_state)` to the
/api/states/:entity_id route alongside existing GET + POST.
Backend curl smoke:
POST /api/states/sensor.test_delete 201
DELETE /api/states/sensor.test_delete 204
GET /api/states/sensor.test_delete 404
Frontend:
components/StateCard.ts +25 LOC — small `×` delete button in the
card's top-right corner. opacity 0 by default, fades in on hover
or keyboard focus. dispatches `hc-state-card-delete` (NOT
`hc-state-card-click`) with stopPropagation so the card's own
click-to-edit handler doesn't also fire.
pages/Dashboard.ts +45 LOC — deletingState (StateView | null), a
confirm modal that names the entity_id in the body, Cancel /
Delete buttons in the footer (Delete styled in muted red),
`_confirmDelete()` dispatches DELETE with bearer, toast on
success, grid refresh.
Browser-verified end-to-end on real homecore-server :8123:
- Hover card → × button visible
- Click × → DELETE confirm modal (NOT edit modal — stopPropagation works)
- Modal names entity_id in code block
- Cancel: entity preserved, modal closes
- Delete: backend GET-after-DELETE returns 404, grid card vanishes,
toast "Deleted sensor.delete_target"
- 0 unexpected console errors (1 expected 404 from verification fetch)
Co-Authored-By: claude-flow <ruv@ruv.net>
|
||
|---|---|---|
| .. | ||
| src | ||
| .gitignore | ||
| README.md | ||
| index.html | ||
| package-lock.json | ||
| package.json | ||
| tsconfig.json | ||
| vite.config.ts | ||
| vitest.config.ts | ||
README.md
@ruvnet/homecore-frontend
HOMECORE web UI — built with Lit 3, TypeScript, and Vite. Design system mirrors the cognitum-v0 / v0-appliance dashboard (ADR-131).
Quick start
cd frontend
npm install
npm run dev # http://localhost:5173
The Vite dev server proxies /api → http://localhost:8123, so you need a
homecore-api-server (or the wifi-densepose-sensing-server crate) running on :8123.
Scripts
| Script | Description |
|---|---|
npm run dev |
Start Vite dev server on port 5173 |
npm run build |
TypeScript compile + Vite production bundle → dist/ |
npm run lint |
ESLint on src/ |
npm test |
Vitest unit tests (3 suites, jsdom) |
Package layout
frontend/
src/
api/
client.ts # fetch + WebSocket client (REST + WS)
types.ts # TypeScript types matching homecore-api JSON shapes
components/
AppShell.ts # <hc-app-shell> — header + nav + content slot
StateCard.ts # <hc-state-card> — single entity state card
icons/
lucide.ts # Tree-shaken Lucide icon wrapper
styles/
tokens.css # 16 CSS custom properties (--hc-*)
base.css # Typography reset, page shell, nav layout
__tests__/ # Vitest unit tests
index.html # Shell loading src/main.ts
vite.config.ts
tsconfig.json
vitest.config.ts
Design system
Colors, typography, and components mirror the cognitum-v0 dashboard
(http://cognitum-v0:9000/). Dark-only; no light-mode. Key tokens:
--hc-primary#19d4e5— teal (active nav, focus ring, CTA borders)--hc-accent#26d867— green (success, secondary CTA)--hc-bg#0b0e13— near-black navy page root- Font: Outfit (display) + JetBrains Mono (mono)
- Icons: Lucide (SVG,
stroke: currentColor, no icon font)
See docs/design/HOMECORE-FRONTEND-design-recon.md for the full recon.
Architecture notes
- Components are standard Lit
LitElementcustom elements — compatible with any HTML page and with Home Assistant's Lit-based frontend. - The REST client uses
fetch; the WS client usesWebSocket. Both accept a bearer token and are fully typed against the Rusthomecore-apiJSON shapes. - WASM:
vite.config.tsenables.wasmasset import. Hook up via dynamicimport('/path/to/module.wasm?init')when WASM bindings are ready.