Jean-Christophe Amiel
Jean-Christophe Amiel
For reference, benchmark for parsing a 25M JSON document with `serde_json` vs `hurl_core`: There is currently a x10 diff in defavor of `hurl_core`, we should set a max x2 compared...
Yes, we plan to be use more complex expression in template, variable etc like: ``` POST https://foo.com { "records": [ { "message": {{ my_var base64Encode }} } ] } ```...
If `token_to_redact` is write in plain text, cristal clear, is it a secret?
Fixed in curl with , we'll have to wait for 8.16.1
Hi @chrisguest75, unless I've mistaken your point, you can do this with [`--output`](https://hurl.dev/docs/manual.html#output): ```hurl GET https://foo.com [Options] output: response.bin HTTP 200 ```
@Nezteb the issue is not open to contribution, but still open, we'll do it.
@lepapareil @fabricereix quick questions about the feature, I would like your opinions: - I'm thinking about two more options: `--pretty` and `--no-pretty`. By default, and in interactive session, we'll prettify...
With "implicit" prettify, we prettify the body if the content is JSON and do nothing otherwise. We'll have a small penalty for trying to parse JSON in anycase. Maybe we...
@fabricereix @lepapareil Now that we have an "easy" way of pretty printing JSON, I see two places where we could also use it(or not): - `--error-format`: with `--error-format long` we...
Ok for the log, and for `--error-format long`? We're displaying colored response headers and the HTTP response as well