Hi @danny-dainton,
In Windows, Ctrl + K followed by Ctrl + 0 is used to collapse items. However, Ctrl + K alone opens the search window, so when I try to collapse items, I often end up with the search window instead. Am I doing something wrong?
Hey @mohdryad
Welcome to the Postman Community!
How do you currently have your keyboard shortcuts setup - You can customize them in the Desktop Client form the > Settings > Shortcuts option menu. Hovering over each one will allow you to change it to something that works for you.
For me on my Mac, the default expand/collapse of items in the sidebar is left and right arrows on their own, as long as the focus is on the sidebar.
me too, Alt + ā , collapse all not work. And i alter shortcut else also not work
Can you provide more visual examples of this please?
You should be able to use just the arrow keys, when the sidebar is in focus.
Are your talking about something in the UI, a short recording will help us to see the issue better.
Iām on mac but I think I have the same issue. Iām heavily using various cmd+K shortcuts (cmd+K followed by a number for collapsing, cmd+K followed by C to comment out parts of my request bodies, cmd+K followed by U to uncomment parts of my request bodies) and they have been working fine for me in postman until now. Now everytime I try to use one of those combinations, the search dialog pops up. I have changed the shortcut for the search (which I never use) to something ridiculous (ctrl + cmd + F) so that it would not interfer with the cmd + K but the search dialog still pops up. This is really annoying.
I made a screen record but as a new user seems like Iām not allowed to upload it.
same issue here with MacOs, I use to comment/uncomment using command+K followed by āCā (comment) or āUā (uncomment), also to collapse the JSON response command+K followed by ā0ā , but now command+K pop ups the Search Bar (annoying) , also tried changing the shortcuts with no luck.
Also those shortcuts mentioned in the Settings for collapsing, are only for the Side Bar, but we are all referring to the JSON response