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 have searched the existing issues for this feature request and I know that duplicates will be closed
Is your feature request related to a problem?
Currently, when working with large or deeply nested JSON structures in the Pretty JSON view in Postman, there is no shortcut or an option to collapse or expand all JSON data elements at once. This can be cumbersome and time-consuming, especially when dealing with large responses that require frequent navigation.
Describe the solution you'd like
I would like to see a feature that allows users to collapse or expand all data elements at once in the Pretty JSON view. This could be implemented as a keyboard shortcut or an option in the UI, similar to the functionality found in many code editors. This feature would improve the user experience, making it easier and more efficient to navigate large or complex JSON responses.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is there an existing request for this feature?
Is your feature request related to a problem?
Currently, when working with large or deeply nested JSON structures in the Pretty JSON view in Postman, there is no shortcut or an option to collapse or expand all JSON data elements at once. This can be cumbersome and time-consuming, especially when dealing with large responses that require frequent navigation.
Describe the solution you'd like
I would like to see a feature that allows users to collapse or expand all data elements at once in the Pretty JSON view. This could be implemented as a keyboard shortcut or an option in the UI, similar to the functionality found in many code editors. This feature would improve the user experience, making it easier and more efficient to navigate large or complex JSON responses.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: