mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 17:26:03 +03:00
[GH-ISSUE #204] On Save Update existing API #75
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#75
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sheecegardezi on GitHub (Oct 22, 2019).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/204
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.
@liyasthomas commented on GitHub (Oct 22, 2019):
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 🙌🏼
@liyasthomas commented on GitHub (Oct 22, 2019):
Btw, if the request is already saved, saving again it will ask you to update the existing API. This is already implemented.
Alternatively, if you want to save the API as a new one, please choose another collection or folder to save it as a new entry. This is also available right now.
Let me know if you're facing any bugs.
@liyasthomas commented on GitHub (Oct 24, 2019):
#209 fixes this, hence closing.
@sheecegardezi commented on GitHub (Oct 31, 2019):
step 1: Run a request
step 2: Create collection and folder
step 3: save the request as test 1
step 4: The request is saved as expected
step 5: Make some changes to API and press save
step 6 : A new request got saved rather than updating the existing one
How do I make changes to an existing request and update it rather than creating a new entry?
@liyasthomas commented on GitHub (Oct 31, 2019):
Work around:
step 6:select test request (already saved from step 5) and save.
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.
@sheecegardezi commented on GitHub (Oct 31, 2019):
Thank you, I was selecting the collection the folder but not the request :D
Cheers,
@cortopy commented on GitHub (Jan 23, 2020):
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
@liyasthomas commented on GitHub (Jan 23, 2020):
@cortopy can you please explain excatly what is not working at your end?
@cortopy commented on GitHub (Jan 23, 2020):
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:
@liyasthomas commented on GitHub (Jan 23, 2020):
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?
@liyasthomas commented on GitHub (Mar 9, 2020):
Closing due to inactivity