99c78f512c
CRUD increment 5/6. Each service pill on the Services page now has
a `▶ Call` button that opens a modal letting the operator POST a
JSON service_data payload to /api/services/<domain>/<service> and
inspect the round-tripped response.
Modal contents:
- heading "Call <domain>.<service>"
- target URL displayed as code (POST /api/services/...)
- service_data JSON textarea (default `{}`, live-validated as
JSON object — same rules as EntityForm.attributes)
- response <pre> block: green border on 2xx, red on non-2xx,
pretty-printed JSON when parseable
- Close + Call buttons in footer; Call disabled on invalid JSON
or while pending; renders "Calling…" briefly during the POST
Reuses `<hc-modal>` from iter 1. No new components — all of iter 5
lives in `frontend/src/pages/Services.ts` (~140 LOC delta).
Browser-verified end-to-end against homecore-server (13 services
seeded across 6 domains):
- 13/13 service pills have a `▶ Call` button
- Modal opens with correct heading and target URL
- Live validation: [1,2,3] → red "must be a JSON object";
`{broken json:` → red "JSON parse: …"; valid → green ✓
- Call button disabled on invalid input
- Successful call: green-bordered response containing
{"called":"switch.turn_on", "acknowledged":true,
"service_data":{"entity_id":"light.kitchen_ceiling","brightness":200}}
- Toast "Called switch.turn_on → 200"
- homecore.ping with empty body (default {}) succeeds too
- 0 console errors related to this flow
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.