Skip to content
New issue

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 Request Keys Do Not Respect Variable Substitutions #3593

Open
Enoz opened this issue Jan 15, 2025 · 0 comments
Open

JSON Request Keys Do Not Respect Variable Substitutions #3593

Enoz opened this issue Jan 15, 2025 · 0 comments
Labels
bug Something isn't working
Milestone

Comments

@Enoz
Copy link

Enoz commented Jan 15, 2025

What is the current bug behavior?

JSON Keys in request object does not follow expected variable replacement logic
Related: #3592

Steps to reproduce

POST https://postman-echo.com/post
[Options]
variable: mykey="variable_value"
{
    "hardcoded_key": "hardcoded_value",
    "{{mykey}}": "some_other_value"
}

What is the expected correct behavior?

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"
}

Execution context

  • Hurl Version (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
@Enoz Enoz added the bug Something isn't working label Jan 15, 2025
@jcamiel jcamiel added this to the 6.1.0 milestone Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants