Conversation
…o router
The assistant sidebar bridge now includes an optional `search` field on
navigate events. Previously query params were embedded in the path string,
but TanStack Router's navigate({ to }) ignores query params in the to
option — they must be passed via the search option.
- Add `search?: Record<string, string>` to SidebarEventMap navigate type
- Destructure { path, search } in the bridge emit handler
- Pass search to router.navigate({ to, search }) in navigateRef
Companion to ollie-assist PR that updates the SITEMAP and NavigatePayload.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
📋 PR Linter Failed❌ Invalid Title Format. Your PR title must include a ticket/issue number and may optionally include component tags (
Example: ❌ Missing Section. The description is missing the ❌ Missing Section. The description is missing the ❌ Missing Section. The description is missing the ❌ Missing Section. The description is missing the ❌ Missing Section. The description is missing the |
📋 PR Linter Failed❌ Incomplete Issues Section. You must reference at least one GitHub issue ( |
Details
The assistant sidebar bridge now includes an optional
searchfield on navigate events. Previously query params were embedded in the path string, but TanStack Router'snavigate({ to })ignores query params in thetooption — they must be passed via thesearchoption.search?: Record<string, string>to theSidebarEventMapnavigate event type inassistant-sidebar.ts{ path, search }in the bridge emit handlersearchtorouter.navigate({ to, search })so TanStack Router correctly applies query paramsCompanion PR: ollie-assist#150 — updates the SITEMAP to V2 project-scoped paths and sends
searchas a separate field in theNavigatePayloadSSE event.Issues
OPIK-5399
Testing
?logsType=tracesChange checklist
Documentation
No documentation changes needed — this is an internal bridge contract update between the assistant sidebar and the host app.
🤖 Generated with Claude Code