mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #4321] [feature]: Create new requests without siphoning data from the previous one #1571
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#1571
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 @GetPsyched on GitHub (Sep 2, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4321
Originally assigned to: @anwarulislam on GitHub.
Is there an existing issue for this?
Summary
When I create a new request, I want that I make a new clean request that doesn't have its body or URL copied over from some previous request.
Why should this be worked on?
This does more harm than good because I end up removing everything most of the time; scenarios where I actually keep some of the old stuff is quite rare, which makes the current behaviour quite annoying.
@liyasthomas commented on GitHub (Sep 3, 2024):
This is a good feature request. Since now we have the ability to duplicate a request, I think creating a new request should start with a fresh context.
While we prioritise this feature for next release candidates, you can use the keyboard shortcut
Ctrl/Cmd+Ito reset the current active request to its default context without manually clearing each one.@GetPsyched commented on GitHub (Sep 3, 2024):
Thanks for the handy shortcut!
@jamesgeorge007 commented on GitHub (Apr 3, 2025):
Hi, closing this issue as it's addressed in the latest release. Please feel free to let us know if you have any feedback.