Jean-Christophe Amiel

Hi @christopheblin regarding the size of the HTML report, which can be an issue, we proposed to intoduce a new option `--max-body` which will be the maximum number of bytes...

Hi @glb-cblin Currently, there is no way to inject data in a Hurl file appart from variable. Like with filter, we're going to introduced _generators_ that will allow this usecase:...

Hi @glb-cblin the generators feature is still not implemented, the closed issue was a try to have a meta "issue" for grouping relating issues. We've now switch to grouping related...

Hi, Currently no but we could implement `--header` option from curl: ``` $ hurl --header a:b test.hurl ``` Will add a header `a` to every request of test.hurl. We could...

You have also `--error-format=long` that prints body response and headers in case of errors

So there are two options: - for debugging purpose, one can use `--error-format=long` to display response body and response headers and failed error. This is already supported in Hurl 4.0.0...

@Lythenas a small workaround for this issue is to use `--output` on a request: ```hurl # Output response to standard output using `-` GET https://foo.com [Options] output: - GET https://bar.com...

Interesting problem! We can see how to adapt the current syntax to deal with it.

Another possibility 😊: use `or` with predicates values. It can works with existing predicates: ```hurl GET https://foo.com HTTP 200 [Asserts] jsonpath "$.name" == "toto" or "tata" headers "Content-type" contains "text"...

`in` is cool, the only thing that make me tickle is that all our current predicates are at the 3rd person `startsWith`, `endsWith`, `contains`, `includes`, `matches`, `exists`, `isBoolean`, `isCollection`, `isDate`,...