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
More and more nowadays we are accustomed to this "auto-save behavior".
However, for the collections, it would feel weird to me that a saved query (i.e., a blueprint) was "randomly replaced" by a temporary "playground" modification
The text was updated successfully, but these errors were encountered:
@imolorhe Mainly what he's saying is that Once you save a collection, the Save button should be disabled. and enabled again if you change the request/query - that's to say check if it's changed and the user may want to save this change.
Example from Postman
When I change the request
I'm checking the possible first contribution to an open-source project.
And this might be a good start, I will check the repo locally and see If I can do that till I get your good-to-go confirmation. and any hints that might help me achieve that.
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Save button changes color
Actual behavior
Save button stays black/gray
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
More and more nowadays we are accustomed to this "auto-save behavior".
However, for the collections, it would feel weird to me that a saved query (i.e., a blueprint) was "randomly replaced" by a temporary "playground" modification
The text was updated successfully, but these errors were encountered: