![]() Until it is fixed, it should be reopened. I'll ask again: What is the status of this issue? Fixing this should be prioritized. The many comments of people stumbling over the current behavior should be prove enough, that it is unexpected. It should only be closed, after it has been resolved. So at a first step, please reopen this issue. Closing this issue for What is the status of this issue? It has been closed, but it seems that nothing has been done about it. We've passed the feedback to our internal teams and we'ld be looking at how to make these more intuitive in upcoming releases. I think it would be more intuitive to duplicate the current (even unsaved) state of the request, instead of the saved stated though. I hope it helps the next person.ĭuplicate did not work for me as described.Īfter explicitly saving the request I wanted to duplicate, it worked as expected. ![]() Any of this message could be factually incorrect. The above is the result of my experience and trying to read the Postman documentation. Click on the orange circle as often as you like, but it will do nothing.Save (Command-S, Control-S, or click the Save button) after every change to a request in a tab.The bottom line is to follow some simple rules: This is why the Duplicate functionality appears broken: the wrong version fo the request is being duplicated. If at this point you Duplicate a collection request, the duplicate will be of the state before you made the changes to the tab. No matter how many times you click on the orange circle, the changes will not be saved. If you click on a collection request and then make changes to it, the changes are only within the tab, not the collection request. With the single remaining tab, save it and the changes will be reflected back to the collection request. If you want to keep the changes in one of the tabs, exit every other tab for the same request and discard changes. If none of the tabs have changes that you want to keep, exit every tab and click the option to discard changes. When this happens, Postman becomes confused as to which tab has the correct changes and all of the tabs tied to a particular collection request will have in the name, In this situation you have two options. ![]() At this point, the collection request is identical to the tab, and therefore the orange dot is removed from the tab.įor reasons unknown, it is possible for the same collection request to spawn multiple tabs. ![]() When you save either by the keyboard or the Save button, the changes in the tab are applied to the request in the collection. I cannot understand why auto-save is not available nor why it is not mandatory. I have made Command-S (the Save shortcut) a regular part of my routine in Postman. If you click the Save button on the right near the top of the screen (something I never bothered to do), you will save the request in the current tab back to the request in the collection on the left. I was doing nothing by clicking the orange circle. I kept clicking on this circle thinking I was saving the requests in the collections. When you click on the orange Yin/Yang circle at the top, nothing happens, despite the mouse hover text being, "Sync your API requests across devices." Clicking this circle saves nothing. This is where the danger lies and where I got into trouble. If the tab has an orange dot, then the request in the tab has changed from the request in the collection. When the request is sent or any changes are made, the tab name is in normal text, indicating that the tab is now decoupled from the request in the collection. Initially, the text in the tab name is italicized, indicating that nothing has been done. When clicking on a request in a collection, a new instance (aka tab at the top) is created. The tabs at the top are instances of collection requests. From what I now understand (I could be wrong), the requests on the left side of the screen are collection requests. I have learned more about this issue and think I know what is going on.
0 Comments
Leave a Reply. |