When part of commented out Json Raw body is uncommented it fully gets uppercased

[emilianopenedo]

trafficstars

Describe the bug When part of commented out Json Raw body is uncommented it fully gets uppercased

To Reproduce Steps to reproduce the behavior:

1. Go to 'Json Raw Request Body'
2. Click on 'Ctrl+k + Ctrl+c' to comment Json block
3. Click on 'Ctrl+k + Ctrl+u' to uncomment Json block (selected text, more than single cursor position)
4. See error, the uncommented block converted to uppercase

Expected behavior Keep original Json case unchanged

App information (please complete the following information):

• App Type Native App
• Postman Version v7.33.1
• OS: Microsoft Windows [Version 10.0.19041.330]

[DannyDainton]

Hey @emilianopenedo

Are you able to provide a short recording of this happening in the app, please?

[ritwijsinha]

Hey @emilianopenedo,

Thank you for reporting this. We were able to reproduce the bug on Windows. As a workaround, can you please try using Ctrl + / to comment/uncomment blocks?

Cheers 🎉

[emilianopenedo]

Hey @emilianopenedo,

Thank you for reporting this. We were able to reproduce the bug on Windows. As a workaround, can you please try using Ctrl + / to comment/uncomment blocks?

Cheers 🎉

Thank you @ritwijsinha I've tried with Ctrl + / with no success. I't seems that the shortcut mappings are the same as VSCode, then I've found that using Ctrl + ç works with my keyboard distribution (sp intl) and keeps the case as expected.

[ghost]

This is becoming quite annoying that it still hasn't been fixed. Ctrl + / doesn't work. It just opens settings on my end.

[MarkusSeb]

Postman developer are not able to fix this issue. Workaround: use shift-alt-mouse click to select slashes and remove

[qfyra]

Found this issue today. I find it very peculiar that this is still an issue.

[giridharvc7]

I can see Ctrl + / working, can someone verify if this is still a problem?

[hammad1-byte]

I can see ctrl + / working, I guess for postman we have to use 'ctrl + / for comment/uncomment both. As we are developers and most of other code editors use 'ctrl + k , ctrl + c to comment and ctrl + k, ctrl + u to uncomment the code. :)

[TiagoSantosDeveloper]

Hello! =)

Everything indicates that it is a conflict of shortcuts.

The software needs to differentiate that Ctrl+K+U is for comment only and Ctrl+U is for uppercase text. Not both at the same time.

[felipedrumond]

This is still a problem. Some APIs won't recognize the values if they are not normalizing the values internally.

[aureole82]

@postman-staff What's the problem?

Either kick Ctrl+K,Ctrl+U (bad for Visual Studio Code users) or kick uppercasing by Ctrl+U! You cannot have both!

[Viltersten]

The amount of times an average developer uncomments is by any measure vastly larger than when they desire to upper case. Even SQL folks started nowadays to make the code NOT SHOUT at us...

[leandrosa]

I think it depends of the layout of the keyboard. For me for example, it worked with Ctrl + ~ to comment and uncomment.

[SyedAzeemJaved]

The issue also occurs on Linux (Pop!_OS 22.04 LTS)

[farhanalie]

This is still a problem, after going through the comments I tried Ctrl + / and Ctrl + ~ which didn't work for me on Swedish keyboard. What worked for me is Ctrl + '.

[MarkusSeb]

thank you very much. It works