mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #3782] [feature]: Sort / Order Environment Variables Alphabetically #1320
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#1320
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 @otezz on GitHub (Jan 27, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3782
Is there an existing issue for this?
Summary
Introduce a functionality within the environment variables section that enables users to sort variables alphabetically. This would greatly simplify the navigation and identification of variables, particularly for users with a large number of environment variables.
Why should this be worked on?
We're starting to move from postman to Hoppscotch, but it seems there's no way to sort the environment variables alphabetically. We have 40+ environment variables on postman and a functionality to sort environment variables would significantly enhance our ability to manage and utilize these variables effectively within Hoppscotch.
@ighoshsubho commented on GitHub (Feb 4, 2024):
I would like to work on this issue.
@liyasthomas commented on GitHub (Feb 4, 2024):
Hi @ighoshsubho, thanks for showing interest in contributing to Hoppscotch.
Can you start a discussion thread to discuss your approach to implementing this feature, so that we can help you better understand the scope of this one?
@ighoshsubho commented on GitHub (Feb 4, 2024):
Sure
On Sun, Feb 4, 2024 at 11:17 AM Liyas Thomas @.***>
wrote:
@ighoshsubho commented on GitHub (Feb 4, 2024):
@liyasthomas started a discussion #3802