You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've searched existing issues and found nothing related to my issue.
Describe the bug
Using bruno 1.17.0.
I'm sending a request to an endpoint that returns a tabular format as text/plain. Then I modify the request to ask for JSON back and the response is returned in application/json.
What's happens:
The response with the JSON content type doesn't get highlighted/validated as JSON. If I switch to some other tab in the response panel, like the Headers tab or Timeline tab, and then back to the Response tab, the editor starts using the correct highlighting/validation for JSON. This workaround also works if I switch to another request tab and then back to the original tab that I'm testing with.
This issue is not specific to the JSON content type, for example if the original response is JSON and the second response is for example XML, the response editor will show a validation error because the returned XML is not valid JSON and will highlight it as JSON.
What should have happened:
The response editor should detect that the response content type is different and apply the appropriate syntax highlighting/validation instantly.
Thanks
.bru file to reproduce the bug
No response
Screenshots/Live demo link
The text was updated successfully, but these errors were encountered:
I have checked the following:
Describe the bug
Using bruno 1.17.0.
I'm sending a request to an endpoint that returns a tabular format as
text/plain
. Then I modify the request to ask for JSON back and the response is returned inapplication/json
.What's happens:
The response with the JSON content type doesn't get highlighted/validated as JSON. If I switch to some other tab in the response panel, like the Headers tab or Timeline tab, and then back to the Response tab, the editor starts using the correct highlighting/validation for JSON. This workaround also works if I switch to another request tab and then back to the original tab that I'm testing with.
This issue is not specific to the JSON content type, for example if the original response is JSON and the second response is for example XML, the response editor will show a validation error because the returned XML is not valid JSON and will highlight it as JSON.
What should have happened:
The response editor should detect that the response content type is different and apply the appropriate syntax highlighting/validation instantly.
Thanks
.bru file to reproduce the bug
No response
Screenshots/Live demo link
The text was updated successfully, but these errors were encountered: