[GH-ISSUE #1525] Improve save request flow #484

Closed
opened 2026-03-16 15:37:40 +03:00 by kerem · 4 comments
Owner

Originally created by @uiosun on GitHub (Mar 3, 2021).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/1525

  1. create two api - "Edit user info" and "Delete user";
  2. refesh page;
  3. choice "Delete user" api and change something;
  4. save use Ctrl + S, show me a default panel;
  5. I'm trance and choice "Edit user info" and save.
  6. congratulation! now, I has two "Delete user".... 😂

I think the tool has good, but in there, the feature puzzled me, and I want to work something, I think:

  1. like Postman, in user save api, show the api panel -- if user want to "save as...", user can choice self need.
  2. oher choice: if he want replace a old api, tool should show a confirm panel.

If has other suggestion, please tell me. and I want to write the feature, Can I?

Originally created by @uiosun on GitHub (Mar 3, 2021). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/1525 1. create two api - "Edit user info" and "Delete user"; 2. refesh page; 3. choice "Delete user" api and change something; 4. save use Ctrl + S, show me a **default panel**; 5. I'm trance and choice "Edit user info" and save. 6. congratulation! now, I has two "Delete user".... 😂 I think the tool has good, but in there, the feature puzzled me, and I want to work something, I think: 1. like Postman, in user save api, show the api panel -- if user want to "save as...", user can choice self need. 2. oher choice: if he want replace a old api, tool should show a confirm panel. If has other suggestion, please tell me. and I want to write the feature, Can I?
kerem 2026-03-16 15:37:40 +03:00
  • closed this issue
  • added the
    feature
    label
Author
Owner

@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.

<!-- gh-comment-id:791388111 --> @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.
Author
Owner

@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.

<!-- gh-comment-id:791561970 --> @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.
Author
Owner

@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.

<!-- gh-comment-id:791774197 --> @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.
Author
Owner

@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.

<!-- gh-comment-id:908155660 --> @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 [ <kbd>Ctrl</kbd><kbd>S</kbd> ] updates to a request in collection. - Click on the "save drop-down" to save as [ <kbd>Ctrl</kbd><kbd>Shift</kbd><kbd>S</kbd> ] another new request in collections.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hoppscotch#484
No description provided.