fix: query parameters containing a colon (:) are not parsed correctly when changed #3045
+46
−4
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.
Description
After saving the request, the colon (
:
) in a parameter name is being consumed by bru parser and what follows is treated as parameter value - so there must be a way to allow either quoting bru keys, or escaping problematic characters. In this PR I introduce a way to store dictionary keys for query params quoted. The quotes are discarded when loading collections, so they will be invisible in the UI.fixes #3037
fixes #2810 (alternative to #2898)
fixes #2878 (alternative to #2898)
Automatic quoting is currently only applied when saving query parameters. It does not make a lot of sense for request headers, where colon is disallowed by HTTP spec. It may make sense to add in multipart-form body key-value table and vars table (#3178).
Example
Screencast.from.2024-09-14.00-41-20.mp4
Contribution Checklist: