We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If there's a space in the name of any query string parameter, the .bru file doesn't load, and the request doesn't appear in the UI.
.bru
Save the attached .bru contents to a file inside a bruno directory and relaunch the app. Note that the request is not loaded.
Using an external editor, change the space between sort descending to an underscore and relaunch the bruno app. Note that the request now appears.
sort descending
Why are QS params stored in 2 different places in the file? Why not store them in one place and then either encode or decode them at load time?
meta { name: Test Request type: http seq: 1 } get { url: https://mydomain.com?sort%20descending=yes%20affirmative body: none auth: none } params:query { sort descending: yes affirmative }
There's nothing to show because the GET request doesn't appear in the interface.
The text was updated successfully, but these errors were encountered:
ganesh-bruno
anusree-bruno
Successfully merging a pull request may close this issue.
I have checked the following:
Describe the bug
If there's a space in the name of any query string parameter, the
.bru
file doesn't load, and the request doesn't appear in the UI.Save the attached
.bru
contents to a file inside a bruno directory and relaunch the app. Note that the request is not loaded.Using an external editor, change the space between
sort descending
to an underscore and relaunch the bruno app. Note that the request now appears.Side Note
Why are QS params stored in 2 different places in the file? Why not store them in one place and then either encode or decode them at load time?
.bru file to reproduce the bug
Screenshots/Live demo link
There's nothing to show because the GET request doesn't appear in the interface.
The text was updated successfully, but these errors were encountered: