Edward Surov

Hi, @BrekiTomasson ! In my case I had been solving a problem of providing typed access to query parameters. In my case, query `?foo=&bar=1` should interpret `foo` parameter as null,...

In my case, I had to made a "quick-n-dirty" solution: 1. I wrote custom `MessInterface` implementation. 2. It's constructor accepted two `MessInterface` instances: for original value (`$nestedAccessor`) and for default...

> I am a bit concerned with the cognitive load one should bear once we introduce some additional value provider abstraction Most users will never deal with it. It's only...

The semantic of both methods is like "add/set (each of) headers". The "add" behavior is perfectly obvious, the "set" behavior is indeed a bit misleading, because it's not obvious -...

Another idea is renaming current `setHeaders()` into `replaceHeaders()` and making `setHeaders()` work as simple setter.

At least we can implement `clearHeaders()` to ensure removing headers that are already set.

Well, @mikepsinn, could you please provide more information about your configuration and library versions?

> I'm still using PHPUnit 7.5.20 That's quite old version. Our v2 prototype supports only PHPUnit 9/PHP 8. Allure extension just uses directory that is set by PHPUnit, maybe old...

Fixed with #64, issue can be closed.

My [remorhaz/php-json-path](https://github.com/remorhaz/php-json-path) supports returning paths (with one of [these methods](https://github.com/remorhaz/php-json-path/blob/master/src/Processor/ProcessorInterface.php#L20-L22) of processor). But I don't think that checking this behaviour is of big value: the main problem is that different...