Broken Undo Functionality (7.36.0)

[jleahy2]

---

Description

I often use Collections to save/work on APIs. I use the Body tab under POST with JSON key/value pairs. I will often remove parts of a key to check the API works, then send the request, check the output, and then push command+z (or undo) to bring the collection back to where it was before I modified it so I can try other combinations.

This used to work perfectly prior to this version, however, this latest update to POSTMAN (version 7.36.0) seems to have somehow broken the Undo/Redo functionality after clicking send. Now, after you click send, if you go to 'undo' (or command+z) the Value field on the Body tab, it blanks/clears the entire field out.

---

Steps to reproduce

• Create new POST, enter URL
• Go to Body tab
• Enter data into Value Field (notice you can edit the data in the field, and push Command+z to undo those changes as expected)
• Leave some data in the field, but remove part of it (so you have something to undo)
• Click Send Button
• Go back to Value Field
• Push command+z (or undo)
• POSTMAN blanks/empties the entire Value field out (instead of undoing the last change as expected).

---

Environment Information

• OSX 10.14.6
• POSTMAN 7.36.0 Native Desktop App

[DannyDainton]

Hey @jleahy2

Thanks for reporting this - I was able to reproduce the issue in the latest version and see the expected behaviour in an earlier version. I don't believe that it's limited to just the POST request body as it seems to be the behaviour for all of the key/value fields in the app.

I'm going to raise this issue with the team and we'll update here when we have more information.

[m3dbedb]

I can confirm undo works incorrectly. Postman 8.6.0, windows 32.
to reproduce:

1. open any collection
2. copy any request
3. drag any request
4. press edit -> undo
5. nothing happens