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
As written in the Hurl grammar, multiline strings and one line strings should support Hurl unicode literals:
POST https://foo.com ``` Un bon caf\u{e9}! ```
equivalent to:
POST https://foo.com ``` Un bon café! ```
One line strings should be OK also:
POST https://foo.com `Un bon caf\u{e9}!`
equivalent to
POST https://foo.com `Un bon café!`
Multiline strings with "Langage hint" also work:
POST https://foo.com ```json { "word" :"Un bon ca\u{e9}!" } ```
While, in the last case, it should be more idiomatic to use a JSON body with JSON unicode literals:
POST https://foo.com { "word" :"Un bon ca\u00e9!" }
Note: we don't support Hurl unicode literals in JSON body as it may add confusion with JSON unicode literals \u{e9} vs \u00e9
\u{e9}
\u00e9
The text was updated successfully, but these errors were encountered:
No branches or pull requests
As written in the Hurl grammar, multiline strings and one line strings should support Hurl unicode literals:
equivalent to:
One line strings should be OK also:
equivalent to
Multiline strings with "Langage hint" also work:
While, in the last case, it should be more idiomatic to use a JSON body with JSON unicode literals:
The text was updated successfully, but these errors were encountered: