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
While using Bruno I expected that the response frame displays the response as it was received.
Today I learned that the contents of this frame can be modified by JavaScript:
As you can see above, the JavaScript code changes the displayed contents of the frame (marked green). When you delete the marked line of code in the tests section and rerun the request, the marked property will not be displayed anymore.
My expectation is that Bruno displays the response as it was received. This display should not be modifiable by any JavaScript code. Otherwise I can not see the truth about the response because it might be messed up by some code containing errors.
In summary: res.getBody() should return a deep copy of what is displayed in the response frame.
In my opinion this deep copy should be done before returning the reference of the body to make sure that the display of Bruno always reflects the response.
I have checked the following:
Describe the bug
While using Bruno I expected that the response frame displays the response as it was received.
Today I learned that the contents of this frame can be modified by JavaScript:
As you can see above, the JavaScript code changes the displayed contents of the frame (marked green). When you delete the marked line of code in the tests section and rerun the request, the marked property will not be displayed anymore.
My expectation is that Bruno displays the response as it was received. This display should not be modifiable by any JavaScript code. Otherwise I can not see the truth about the response because it might be messed up by some code containing errors.
In summary: res.getBody() should return a deep copy of what is displayed in the response frame.
.bru file to reproduce the bug
Screenshots/Live demo link
.
The text was updated successfully, but these errors were encountered: