feat: prompt variable supported for bruno api docs - #87
Open
sachin-bruno wants to merge 5 commits into
Open
sachin-bruno wants to merge 5 commits into
sachin-bruno wants to merge 5 commits into
Conversation
|
Contributor
|
can you please check the behaviour of nested prompt variables as per parity with app. Screen.Recording.2026-09-23.at.5.49.22.PM.movScreen.Recording.2026-09-23.at.5.51.53.PM.mov |
sundram-bruno
approved these changes
Sep 23, 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
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.
Ref: BRU - 3839
Problem
Prompt variables written as {{?Name}} were not supported in the docs playground, so sending a request that used one shipped the raw token in the URL, headers or body instead of asking the reader for a value.
Fix
The playground now scans each request before it goes out, shows the same Input Required dialog the Bruno app shows, and substitutes whatever the reader types into the URL, headers, params, body and auth.
Screenshots
