feat(oc-docs): resolve variables in playground example and request URLs - #145
Closed
sundram-bruno wants to merge 3 commits into
Closed
Conversation
Render the example view URL through VariableText so {{variables}} show
the docs-style highlighted pill and hover tooltip (name, scope, resolved
value). Replace the playground request URL <input> with HighlightedInput
wired to the variable resolver, so the editable URL paints variable
tokens in the same colour scheme, shows the variable info card on hover,
and offers {{variable}} autocomplete. Add an optional onEnter prop to
HighlightedInput to preserve Enter-to-send, guarded against IME
composition.
Cover the example view URL variable hover card (name, scope, resolved
value) and the request URL bar's variable rendering plus {{variable}}
autocomplete. Adds a QueryBar component object and wires the variable
card and playground environment switcher onto PlaygroundComponent.
sundram-bruno
marked this pull request as draft
July 23, 2026 06:47
…d vars
Drop the brand-tinted pill override on the playground request URL bar so
its {{variable}} tokens use the same valid (green) / invalid (red)
colours as the params and headers cells, instead of a flat brand colour
that hid whether a variable resolves.
Add e2e covering that request-scoped and folder-scoped variables
referenced in the playground resolve as valid (not painted red as
undefined), guarding the scope the ItemVariableResolverProvider must
include.
Contributor
Author
|
to be taken as a separate task with a larger scope. |
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.
Issue : Previously the example and playground request URLs rendered
{{baseUrl}}etc. as plain, uncoloured text with no way to see the resolved value, while the docs request URL bar already resolved and tooltipped them. This brings both surfaces to parity.JIRA : BRU-3753
Resolve
{{variables}}in the playground's example view URL and request (QueryBar) URL, matching the docs behaviour.VariableText, so{{var}}tokens show the docs-style highlighted pill and a hover tooltip (variable name, scope badge, resolved value, copy).<input>is replaced withHighlightedInput, wired touseResolvedVariables(). The editable URL now paints{{var}}tokens in the same colour scheme, shows the variable info card on hover, and offers{{variable}}autocomplete.