The documentation for EntityConstraintViolationListInterface::filterByFields suggests that the result will include the given $field_names, but the opposite is actually the case. The specific part of the documentation that is wrong is:
The returned object just has violations attached to the provided fields.
Perhaps something like this would be better:
The returned object has violations attached to the provided fields removed.
Decide on wording and do!
None.
No change to behaviour, but fixes documentation that is the opposite. I assume this doesn't count as a BC change, as core code is using it correctly, despite the documentation actually being reversed? Either way, something should be done!
None.
Active
11.0 🔥
entity system
Enhances developer experience.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
john.oltman → made their first commit to this issue’s fork.
I ran into this recently and it cost me a debugging session. Let's get this fixed.
I used different text vs the proposed resolution, to be consistent with the verbiage for the related filterByFieldAccess method.