mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #4719] [feature]: Bulk Editing for Environment Variables #1760
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#1760
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 @iDschepe on GitHub (Feb 4, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4719
Originally assigned to: @anwarulislam on GitHub.
Is there an existing issue for this?
Summary
Description:
Currently, Hoppscotch already provides a bulk editing feature for request parameters, which is very useful for quickly managing large sets of data. However, the same functionality is not available for environment variables.
Feature Request
I propose adding a bulk editing option for environment variables and secrets, similar to the one available for request parameters. This would make it easier to:
Proposed Solution
Introduce a bulk edit mode for environment variables and secrets, as already implemented within request parameters.
Why should this be worked on?
This feature would be particularly useful for teams working on APIs with many environment configurations. Since the bulk editing feature already exists for parameters, implementing a similar approach for environments could align with the existing UX pattern.