mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #4515] [feature]: Access to Request in Script #1652
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#1652
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 @cdigruttola on GitHub (Nov 6, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4515
Is there an existing issue for this?
Summary
Access to request body in scripts, similar to Postman pm.request
Why should this be worked on?
Hi,
in Postman I used to access to request body in scripts using pm.request
Is there the possibility to implement this feature?
@jamesgeorge007 commented on GitHub (Sep 30, 2025):
Hi, we've introduced a
hoppnamespace housing new scripting methods as proposed in https://github.com/hoppscotch/hoppscotch/discussions/5221 with the ability to access request properties from the scripting context.It's not recommended to migrate or rework your existing scripts for the new scripting APIs just yet. Breaking changes are expected as the system evolves.
The rollout is intentionally gradual to gather feedback and refine based on real-world use. All future changes will be scoped to the experimental scripting sandbox (enabled by default; can be toggled in
Settings → Experiments). Please feel free to take it for a spin and let us know your feedback via the RFC above.