-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
On Save Update existing API #204
Comments
Collections feature has just been shipped! Thanks for the first set of suggestions. Will surely consider adding these feature requests in near future. In the meantime, you can make use of 'Edit request' feature within collection/folder/ to update API changes. Expecting new feature requests and suggestions as well as bug reports 🙌🏼 |
Btw, if the request is already saved, saving again it will ask you to update the existing API. This is already implemented. Let me know if you're facing any bugs. |
#209 fixes this, hence closing. |
Work around: If there's multiple requests with same name, automatically replacing them results in conflicts. But manually replacing the one we needed will replace the old one with new request label. |
Thank you, I was selecting the collection the folder but not the request :D |
I'm also experiencing this issue. I just can't make it work so that I update an existing request. I click on the request itself, click on save (nothing happens), refresh and the new details do not appear |
@cortopy can you please explain excatly what is not working at your end? |
sure! thanks for the prompt reply @liyasthomas I'm having a hard time updating saved requests. After reading this issue, this is what I've tried:
|
First of all sorry for the inconveniences. I admit saving request are a bit of cumbersome. Here's what I did to reproduce the issue:
Everything worked as I expected. The previous request was replaced by new one. Or am I missing something? |
Closing due to inactivity |
Is your feature request related to a problem? Please describe.
As I am developing my API is evolving. When I make a change in api I have to save the API again and delete the old saved version.
Describe the solution you'd like
When I press ctrl+s (or some other shortcut) save action is triggered.
A background logic checks if I had saved this API before or not.
If its already saved:
-promote to update existing API
-update the changes I have made in the existing API
else:
-promote to save a new API
-save the new API
Describe alternatives you've considered
With each change save a new API and delete the old one from the collection.
The text was updated successfully, but these errors were encountered: