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
{{ message }}
Repository navigation
Commit 421d3c4
Browse filesBrowse the repository at this point in the historyBrowse files
fix(signals): let inspect-signals peek at a component injector
A peek could only target an environment injector, so an agent asking
for the signals of a component that was not the selected one got the
routed graph instead. `inspect-signals` now resolves `component` the
way `highlight` does and takes a CSS `selector`, and a selector that
matches no component host is refused at once.
Refs #367
Copy file name to clipboardExpand all lines: apps/docs/src/content/inspectors/signals.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -229,7 +229,7 @@ Entries are sampled instead of exact in these cases:
229
229
230
230
### Switch the graph from an agent
231
231
232
-
The `pangular:highlight` tool also switches the graph to the component it highlights. The picker does not show that choice. Calling `pangular:inspect-signals` with `root` or a route path reads that injector's graph once and does not change what the Signals page shows.
232
+
The `pangular:highlight` tool also switches the graph to the component it highlights. The picker does not show that choice. Calling `pangular:inspect-signals` with `root`, a route path, a component the page is not showing, or a CSS `selector` for a component host reads that injector's graph once and does not change what the Signals page shows.
233
233
234
234
### Find a stuck effect in a root service
235
235
@@ -244,15 +244,15 @@ The `pangular:highlight` tool also switches the graph to the component it highli
|`pangular:scan-signals`| tool | Signal declarations from source, with signal inputs, models and queries. Pages through a large project with `filter` and `offset`. |
250
-
|`pangular:inspect-signals`| tool | The graph the page reported, with edges, resources and history. Takes a host tag, class name, instance id, `root` or a route path. |
251
-
|`pangular:watch-signal`| tool | Watches a signal and turns write stacks on or off on a page. |
252
-
|`pangular:highlight`| tool | Highlights a component and makes it the target of the graph. |
253
-
|`pangular:signal-graph`| resource | The live graph per page. |
|`pangular:scan-signals`| tool | Signal declarations from source, with signal inputs, models and queries. Pages through a large project with `filter` and `offset`. |
250
+
|`pangular:inspect-signals`| tool | The graph of a component or injector, with edges, resources and history. Takes a host tag, class name, instance id, `root`, a route path or a CSS `selector`. |
251
+
|`pangular:watch-signal`| tool | Watches a signal and turns write stacks on or off on a page. |
252
+
|`pangular:highlight`| tool | Highlights a component and makes it the target of the graph. |
253
+
|`pangular:signal-graph`| resource | The live graph per page. |
254
254
255
-
`inspect-signals`returns the graph of the chosen component. Call `highlight`first to switch it to another component. See [Tools](../agents/tools.md).
255
+
`inspect-signals`reads the graph of the component or injector you name, without switching the Signals page. Call `highlight` to switch the page itself. See [Tools](../agents/tools.md).
return`No component host matches the CSS selector \`${selector}\`${pageId ? ` on page \`${pageId}\`` : ''}, so there is no signal graph to read. The selector must match the host element of a component. Pass a class name or instance id from pangular:list-components as \`component\` instead.`;
0 commit comments