New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Editing a saved collection does not indicate that the view is not saved/modified #2425
Comments
Sorry I'm not sure I properly understand the issue. If you have screenshots, those would help too. |
Editing a saved query is not treated as "unsaved".
That is ... sort of my point. There's no visual indication. I'm not sure how screenshots would help in this case. |
@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. I'm checking the possible first contribution to an open-source project. |
That makes sense. @WaseemMansour sure feel free to pick this up! Let me know if you need any help |
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: