mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 09:16:03 +03:00
[GH-ISSUE #2906] [feature]: Better environment variable UX/UI #941
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#941
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 @furier on GitHub (Jan 25, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2906
Is there an existing issue for this?
Summary
As mentioned in #2574 the environment variable UX/UI could definitely improve tenfold. As of now I find it very hard to see at any given time what environment variables I am using, and you need many clicks to check and/or change environment variables.
Support for sub environment variables would also be a great idea.
Similar UI as Insomnia as shown here would be great.

Why should this be worked on?
I am not sure I can get my colleagues to adopt Hoppscotch because of the simple fact that it is nearly impossible to see what environment you are working on and or change it.
Can live without sub environments but it would be such a nice addition to also have that.
@liyasthomas commented on GitHub (Jan 25, 2023):
Kindly suggest any possible UI improvements in #2574.
Since this issue is traced under #2574, I'm closing this ticket.
@furier commented on GitHub (Jan 25, 2023):
@liyasthomas as commented in #2574 it was kindly asked to split all the feature requests in the issue into their own issues! So I did... Because the issue had been dead for months...