mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #3634] [feature]: improve usabilty of replace url parts with environment variable #1257
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#1257
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 @RaHehl on GitHub (Dec 8, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3634
Is there an existing issue for this?
Summary
An internal user reported to me about problems replacing placeholders in URLs:
He already sets the placeholders with a variable name, then he chooses "set as variable"
but the placeholder, which should actually be the variable name, is used as the value
Personally, I don't think this is a bug, but I think that the behavior could be improved here.
I've found that "set as variable" works not only with placeholders but generally with things that you mark. I think a more fluid behavior would be if the placeholder is used as the variable name if there are already existing placeholders, and if parts are simply marked, the value is still transferred to the value field, but then when the part is saved in the URL it is directly replaced with the variable .
Why should this be worked on?
@liyasthomas commented on GitHub (Dec 9, 2023):
Hi @RaHehl, thanks for suggesting this improvement, it seems there's already another issue ticket which could be a duplicate of this. Please track the progress on #3489.