mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #3692] [feature]: set as variable popup appears on test window and wont close on "ESC" button press #1278
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#1278
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 @yvz5 on GitHub (Dec 22, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3692
Is there an existing issue for this?
Current behavior
When I want to write tests and select a text it always shows me the "set as variable" popup window which is very annoying because it doesnt close on "ESC" button press. Furthermore, I don't want to set anything as variable when I am writing a test. I think this popup window should be disabled for the Tests.
Steps to reproduce
TestsTestswindowSet as variablepopup appear and annoy youEnvironment
Production
Version
Local
@liyasthomas commented on GitHub (Dec 22, 2023):
This doesn't seem to be a bug since this is an intended behavior. Selecting any text from editor instances asks the user to set the selected text as an environment variable.
It seems this UX can be improved hence, the ability to disable this pop-up in selective editor instances seems a good idea. Welcome to open discussions.
@yvz5 commented on GitHub (Dec 22, 2023):
yes, sorry for confusion. this might be a good feature request
@anwarulislam commented on GitHub (Mar 5, 2025):
This feature has already been implemented; therefore, I am closing the PR.