Skip to content

Commit 2fc2b2e

Browse files
authored
docs(chat): clarify injectThreadRouting usage prerequisites (#701)
* docs(chat): note injection-context + module-scope signal requirement in thread-routing guide * docs(chat): use <Callout> for the prerequisites note (match file convention, per review)
1 parent b14d4ea commit 2fc2b2e

1 file changed

Lines changed: 4 additions & 0 deletions

File tree

apps/website/content/docs/chat/guides/thread-routing.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,10 @@
22

33
`injectThreadRouting()` binds an app-owned active-thread signal to the Angular Router: it restores the thread id from the URL on load, stamps signal changes back into the URL, validates stale links, and treats a bare URL as "no thread" (the welcome state). **The URL is the sole source of truth — nothing is written to localStorage**, so links remain shareable without any extra plumbing.
44

5+
<Callout type="info" title="Prerequisites">
6+
Call `injectThreadRouting()` from an injection context (a component constructor or field initializer), and declare the active-thread signal at module scope so your `provideAgent({ threadId })` provider can reference it.
7+
</Callout>
8+
59
## What it does
610

711
| Behavior | Detail |

0 commit comments

Comments
 (0)