mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #5615] [bug]: Variables in Request Body Not Detected While URL Variables Work Correctly #2174
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#2174
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 @chhaviG22 on GitHub (Nov 25, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5615
Originally assigned to: @chhaviG22 on GitHub.
Is there an existing issue for this?
Platform
Web App
Browser
Chrome
Operating System
macOS
Bug Description
Environment variables are not being detected or highlighted in request body editors (JSON, XML, GraphQL, etc.), while the same variables work correctly when used in the URL/endpoint field.
What Happened
When using environment variables with the
<<envVar>>syntax in the request body editor:However, the same variables work perfectly when used in the URL/endpoint field, showing proper detection with green highlighting and correct tooltip values.
Expected Behavior
Environment variables should be:
Steps to Reproduce
envVarwith value"test123")<<envVar>>https://example.com/<<envVar>>Screenshots/Video
https://github.com/user-attachments/assets/30245a9b-8c91-4149-82e1-f7f10e81e8fb
Deployment Type
Hoppscotch Cloud
Version
2025.10.1
@jamesgeorge007 commented on GitHub (Dec 11, 2025):
Closing since this is now addressed in the v2025.11.2 release.