mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #1525] Improve save request flow #484
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#484
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 @uiosun on GitHub (Mar 3, 2021).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/1525
I think the tool has good, but in there, the feature puzzled me, and I want to work something, I think:
If has other suggestion, please tell me. and I want to write the feature, Can I?
@liyasthomas commented on GitHub (Mar 5, 2021):
When saving a request if you want to replace / overwrite an existing one, you can choose the previous request in save modal. Let me which workflow works best for you. I didn't quite get what you meant by which operation that need to be corrected.
@uiosun commented on GitHub (Mar 5, 2021):
I try to refresh or open page, the request hold in page, but not has "previous request" in save panel.
Now, I must choice collection、choice folder、choice request.....so hard, don't you think?
So, I suggest autoload previous request, When user need "Save as...", he/she manually choice "/"
In my work, "update request" is frequent, and "new request" is less.
Or add config? user can choice any mode.
Ps: if can't refresh(F5 press), the save panel can autoload previous request, I know it.
@liyasthomas commented on GitHub (Mar 5, 2021):
Thanks for your explanation. Now it makes sense. Flow of overwriting a request is somewhat confusing righ now. We're actually working on a parallel flow where you'll have a UI similar to sidebar Collections. And it'll be easy to choose a previous request in a glance.
Kindly be patient, hoping to get a working prototype by end of next week. I'll let you know when it's up.
@liyasthomas commented on GitHub (Aug 30, 2021):
With the release of v2 - we've introduced "Save" and "Save as" features.
You can now restore and save [ CtrlS ] updates to a request in collection.
Click on the "save drop-down" to save as [ CtrlShiftS ] another new request in collections.