feat(sample-catalog): map invocations_ws protocol to 'Invocations (WebSocket)'#514
Merged
Merged
Conversation
…bSocket)' displayName
This was referenced Jul 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a displayName mapping for the
invocations_wsprotocol id in the sample-catalog generator so the template picker shows Invocations (WebSocket) instead of the raw idinvocations_ws.Why
The protocol dimension in
DIMENSION_DEFAULTSonly mappedresponsesandinvocations. Any other discovered protocol id (likeinvocations_ws) fell back to rendering the raw id, which looked unpolished in the UI.Changes
.github/scripts/generate_sample_catalog.mjs: addedinvocations_ws: 'Invocations (WebSocket)'to the protocol options.Notes
The generated
samples/hosted-agent/sample-catalog.jsonis intentionally left untouched — it is regenerated by the CI sync workflow, which will pick up the new displayName on its next run.