We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JSON Keys in request object does not follow expected variable replacement logic Related: #3592
POST https://postman-echo.com/post [Options] variable: mykey="variable_value" { "hardcoded_key": "hardcoded_value", "{{mykey}}": "some_other_value" }
Expected Request to submit as
{ "hardcoded_key": "hardcoded_value", "variable_value": "some_other_value" }
Current Behavior Request is submitted as
{ "hardcoded_key": "hardcoded_value", "{{mykey}}": "some_other_value" }
hurl --version
hurl 6.0.0 (x86_64-pc-linux-gnu) libcurl/8.11.1 OpenSSL/3.4.0 zlib/1.3.1 brotli/brotli/1.1.0 zstd/zstd/1.5.6 libidn2/2.3.7 libssh2/1.11.1 nghttp2/1.64.0 quic/nghttp3/1.7.0 Features (libcurl): alt-svc AsynchDNS brotli HSTS HTTP2 HTTP3 IDN IPv6 Largefile libz NTLM SPNEGO SSL TLS-SRP UnixSockets zstd Features (built-in): brotli
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What is the current bug behavior?
JSON Keys in request object does not follow expected variable replacement logic
Related: #3592
Steps to reproduce
What is the expected correct behavior?
Expected
Request to submit as
Current Behavior
Request is submitted as
Execution context
hurl --version
):The text was updated successfully, but these errors were encountered: