You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/Inspect-Screen.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -245,6 +245,6 @@ The current graph inspection has deliberate limitations:
245
245
-**No full reachability analysis.** Diagnostics check surface membership but do not trace whether all nodes are reachable through flows or surfaces.
246
246
-**No route-wide graph inspection.**`inspectScreen()` inspects one screen at a time. There is no cross-screen or route-level graph snapshot yet.
247
247
-**No DevTools package yet.** There is no dedicated browser extension or DevTools panel. The web-basic demo uses a `MutationObserver`-driven DOM side panel.
248
-
-**DOM renderer does not expose all semantic IDs as data attributes.**The DOM renderer uses its own `id` conventions for accessibility. Semantic IDs are not yet emitted as `data-semantic-id` attributes.
248
+
-**DOM renderer exposes semantic IDs as opt-in data attributes.**Pass `showSemanticIds: true` to `renderDom()` to add `data-intent-screen`, `data-intent-ask`, and `data-intent-action` attributes to rendered DOM elements. Default output is unchanged.
249
249
-**Resource graph inspection exists.**`inspectScreen()` accepts runtime resource nodes and reports status, staleness, and errors. However, cache and staleness semantics are still early — there is no automatic reload, polling, or TTL-based invalidation.
250
250
-**No visual diff or time-travel debugging.** Graph snapshots are static. There is no history of state changes over time.
Copy file name to clipboardExpand all lines: docs/Quickstart.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -91,15 +91,18 @@ This produces:
91
91
- Typing a valid email enables the button reactively.
92
92
- Pressing Enter triggers the default action when unambiguous.
93
93
94
-
The DOM renderer also accepts services and an option to show the screen name as an `<h1>`:
94
+
The DOM renderer also accepts services and options:
95
95
96
96
```ts
97
97
renderDom(InviteMember, {
98
98
target: root,
99
-
showScreenName: true,
99
+
showScreenName: true, // show screen name as <h1>
100
+
showSemanticIds: true, // add data-intent-* attributes for debugging
100
101
})
101
102
```
102
103
104
+
With `showSemanticIds: true`, the DOM includes `data-intent-screen`, `data-intent-ask`, and `data-intent-action` attributes that map rendered elements back to their `inspectScreen()` semantic IDs.
105
+
103
106
## 4. Test semantically
104
107
105
108
The testing package lets you assert product behavior without touching the DOM:
0 commit comments