Describe the bug
Changes made to requests is not updated in collections
To Reproduce
Steps to reproduce the behavior:
- Open Postman and create simple request
- Create collection and save the API to the collection
- Now, make some changes in the request. For example, change the value for key to a variable and save the request
- But the change is not reflected in collection
Expected behavior
Changes in the request should reflect in the collection where the api is saved
Screenshots
App information (please complete the following information):
- App Type - Native App
- Postman Version - 6.0.1
- OS: windows
When you create a request and don’t give it a name, the app falls-back to using the first URL that you ever enter and save the request.
The moment you’ve given a request a name (or saved it using the first back), then it will no longer update itself (You’ve to explicitly change it, let’s look at the example that follows).
I’d suggest a better practice would be instead of keeping URL’s as names of requests, you should give them descriptions, as to what the endpoint is going to do.
For eg:
1. Get all movies (findAll)
2. Get details of a movie (find)
3. Add a new movie
This is a more readable, understandable and human-relatable format rather than:
1. https://ec2-adasd-22-323sdfdfdf-fdfdsf232-asdasdasd-asdasdasd32323--sadasd.com/get/category/movie/all
2. https://ec2-adasd-22-323sdfdfdf-fdfdsf232-asdasdasd-asdasdasd32323--sadasd.com/get/category/movie/id/234
3. https://ec2-adasd-22-323sdfdfdf-fdfdsf232-asdasdasd-asdasdasd32323--sadasd.com/add/category/movie/new/
Lastly, this isn’t a bug so I’ll be closing this thread.
1 Like