mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #3248] [feature]: Support export of a single environment #1075
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#1075
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 @cjchand on GitHub (Aug 7, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3248
Is there an existing issue for this?
Summary
When clicking the "Export" icon for Environments, there is not an option to choose which environment to export. Instead, all of the Environments are exported in one blob.
When trying to use this file with
hopp test, it results in aMALFORMED_ENV_FILEerror.Why should this be worked on?
For end users that are less technically savvy, this presents a challenge to export the desired Environment to use for CLI testing (e.g.: running a Collection as a functional test suite).
For any user, it causes additional friction to manually carve up the file for the target Environment.
@liyasthomas commented on GitHub (Dec 8, 2023):
It seems this feature is already available in Hoppscotch, hence I'm closing this ticket.