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 kommentar(er)
