Christophe Coevoet
Christophe Coevoet
The default context used by `sanitize` is the `body` context. @tgalopin should we have a `document` context for the case of sanitizing a full document rather than a partial ?
@tgalopin the idea is to be able to support properly the case of sanitizing a `` tag, that can contain both a `` and ``, as done in the reported...
@nex3 what is the status of this fast-track proposal ?
I'm totally in favor of removing support for annotations. However, working on 4.0 should probably justify prioritizing the implementation of a deprecation reporting system (as discussed in https://github.com/Behat/Behat/issues/1574 even though...
What makes things worse is that only part of these settings are documented, making things even harder to configure properly.
As described in the issue, most of those things can be figured out as the current code validates those. But nobody has taken the time to implement them until now.
> Adding |object will allow pass the phpstan error. In this case I don't know another way to resolve this, but it is only affecting to phpstan side. no it...
As I don't know what phpstan warning you are trying to fix, I cannot provide alternative fixes. Please provide the warning being reported.
Once Behat supports proper reporting of deprecations (see the discussion in #1574), Behat could trigger a deprecation for such usage. The solution then would be to use a non-capturing group...
The workflow changes done in the other PR were *not* about bumping the min PHP version (which is what this PR actually does, even if it tries to describe it...