[dashboard-language] Reactive core - #80
Conversation
There was a problem hiding this comment.
Protected files were modified in this pull request and require manual scrutiny before merge.
Please verify that each protected-file change is intentional, policy-compliant, and safe:
- Protected files:
README.md,package-lock.json,package.json
|
@copilot fix infrastructure issues with playwright (use MCP instead of playwright-cli) |
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Updated the dashboard renderer to use the built-in Playwright MCP browser tooling instead of the incompatible |
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Fixed the failing browser check by loading the actual DOM source through a data-URL module import instead of a file:// import from about:blank, which was causing the heading not to render in Playwright. Verified with: |
Caution
Protected files were modified in this change.
This pull request is in
request_reviewmode and requires explicit human scrutiny before merge.Protected files:
README.md,package-lock.json,package.jsonMilestone
Reactive core
Specification coverage
DLS-CONF-004What shipped
pages/dashboard/src/reactive.jswith deterministic reactive state, derived values, effect reruns, and disposal.pages/dashboard/src/dom.jswith a small hyperscript-style DOM builder, attribute/dataset handling, and keyed list reconciliation supporting updates, removals, and reordering.pages/dashboard/PLAN.mdandpages/dashboard/README.mdfor the shipped slice.Quality gates
npm install✅npm run typecheck✅npm run lint✅npm test✅npm run test:e2eBlockers
browserType.launch: Executable doesn't exist). The e2e tests are present, but browser execution could not be completed in this environment.Next milestone
Document model and validation