Max Beckers

Not at the moment, but it could be a great new feature for this lib, thanks for the issue!

@bigfoot90 just a question, did you have this problems on a unix or on a windows environment? I can only reproduce this on windows. /cc @chalasr what I saw on...

@bigfoot90 you're right, there was sth wrong in my vendors. And the enter of the input is the problem you mentioned.

I guess we only have to validate that there is the attribute `checked` on the `input` or even not. More details see here: https://stackoverflow.com/a/4613192

I took a quick look inside. For mee this is working (with the unit tests) and valid: `` and this too: ``. But the checked value seems to be case...

IMHO when we think about schema validation for the `XMLEncoder` then it should not only be implemented for the `encode`. When data is comming into the system it's as well...

@xabbuh im also fine with that. 👍

@nicolas-grekas the difference in 4.4 is from PR #47883 ... so i guess it shoud be rebased to 4.4 and then merged to 4.4?

I'd do that, but I guess I only could create a new PR with the change. So @aleksandr-shevchenko should do the rebase.

@pavol-tuka yes, in the `choice_filter` you have the null value. But did you checkout the view? When you try it the way you said, with required by default: ``` #[Route('/test')]...