Skip to content

Register the conversation history in the WASM demo host too (fixes #119) - #120

Merged
davidnmbond merged 1 commit into
mainfrom
fix/issue-119-wasm-conversation-service
Aug 29, 2026
Merged

Register the conversation history in the WASM demo host too (fixes #119)#120
davidnmbond merged 1 commit into
mainfrom
fix/issue-119-wasm-conversation-service

Conversation

@davidnmbond

Copy link
Copy Markdown
Contributor

Closes #119.

The conversation sidebar and tabs from #111/#112 work locally and are completely absent from the published demo.

PDChat renders the conversation UI only when given an IChatConversationService, and it was registered in only one of the two demo hosts — PanoramicData.Blazor.Web, which is what runs locally. GitHub Pages publishes PanoramicData.Blazor.WebAssembly/Client, which had none. So the demo everyone actually looks at was the one host without the service.

My miss: I verified against the local Web host throughout and never against the artefact the public demo is built from.

Registers the same trio in the WASM client, with a comment in both files saying they must match and why. A shared AddDemoServices() extension would remove the class of bug rather than this instance — noted on the issue.

🤖 Generated with Claude Code

The conversation sidebar and tabs worked locally and were completely
absent from the published demo.

PDChat renders the conversation UI only when it is given an
IChatConversationService, and the service was registered in only one of
the two demo hosts: PanoramicData.Blazor.Web, which is what runs
locally. GitHub Pages publishes PanoramicData.Blazor.WebAssembly/Client,
which had no registration - so the demo everyone actually looks at was
the one host without the service.

Verified throughout against the local Web host and never against the
artefact the public demo is built from, which is exactly how this got
missed.

Registers the same trio in the WASM client, and puts a comment in both
files saying they have to match and why. A shared AddDemoServices()
extension would remove the class of bug rather than this instance; noted
on the issue rather than done here.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@davidnmbond
davidnmbond merged commit f7c100e into main Aug 29, 2026
1 of 3 checks passed
@davidnmbond
davidnmbond deleted the fix/issue-119-wasm-conversation-service branch August 29, 2026 21:14
@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 2 duplication

Metric Results
Complexity 0
Duplication 2

View in Codacy

AI Reviewer: run a review on demand. To trigger the first review automatically, go to your organization or repository integration settings. AI can make mistakes. Always validate suggestions.

Run reviewer

TIP This summary will be updated as you push new changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Conversation sidebar and tabs are missing from the published demo: service registered only in the Web host, not the WASM client Pages builds from

1 participant