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
I often use the ⌘ + / keybind to comment out certain parts of a request that I'm debugging. I recently updated my Bruno version to the latest version though (1.34.2) and this seems to have broken that functionality for XML. Prior to the upgrade, I was using version 1.23.0.
Previously, when using the keybind, it would comment out sections in XML style, wrapping it in <!-- --> or removing the wrapping from a commented-out line or section. Now, it just adds or removes // from the start of the line which produces invalid XML. This is especially annoying in existing Bruno files which have commented-out lines that I'd like to include, as now they need to be commented/uncommented manually.
I suspect this was introduced by #2634, as this made some changes meant to allow the comment keybind to work with JSON, but the behavior might be spilling over to XML editing as well.
I have checked the following:
Describe the bug
I often use the
⌘ + /
keybind to comment out certain parts of a request that I'm debugging. I recently updated my Bruno version to the latest version though (1.34.2
) and this seems to have broken that functionality for XML. Prior to the upgrade, I was using version1.23.0
.Previously, when using the keybind, it would comment out sections in XML style, wrapping it in
<!-- -->
or removing the wrapping from a commented-out line or section. Now, it just adds or removes//
from the start of the line which produces invalid XML. This is especially annoying in existing Bruno files which have commented-out lines that I'd like to include, as now they need to be commented/uncommented manually.I suspect this was introduced by #2634, as this made some changes meant to allow the comment keybind to work with JSON, but the behavior might be spilling over to XML editing as well.
.bru file to reproduce the bug
Example Collection.json
Screenshots/Live demo link
Behavior before updating:
comment_xml_example_before.mov
Behavior after updating:
comment_xml_example.mov
The text was updated successfully, but these errors were encountered: