mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 08:45:58 +03:00
[GH-ISSUE #5836] [feature]: Add user choice for cURL import target - New Tab or Active Tab #2288
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#2288
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 @chhaviG22 on GitHub (Feb 4, 2026).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5836
Is there an existing issue for this?
Summary
Currently, when importing a cURL command, it overwrites the content of the active tab without warning, which can lead to accidental loss of unsaved work. This feature adds two import options in the cURL import modal: "Import in New Tab" (primary action) and "Import in Active Tab" (secondary action), giving users control over where the imported request is placed.
Why should this be worked on?
Problem Statement
When users import a cURL command into Hoppscotch, the current behavior automatically overwrites the active tab's content. This creates several UX issues:
Use Cases
Scenario 1: Testing Multiple Variations
A developer is testing an API endpoint and wants to import several cURL examples from documentation while keeping their original request for comparison. Currently, they must manually duplicate the tab before each import.
Scenario 2: Exploring APIs
When exploring a new API with multiple cURL examples, users want to import each one into separate tabs to compare headers, parameters, and request bodies side-by-side.
Scenario 3: Avoiding Accidental Overwrites
Users accidentally paste a cURL command and lose their carefully crafted request with custom headers and authentication that wasn't saved to a collection yet.
This enhancement aligns with user expectations from other development tools (Postman, Insomnia) where importing typically creates new items rather than overwriting existing work.