Wow, thanks for taking this up so quickly@peterrehm. What do you think about also adding some note to this option in the form reference?

No problem. I have added this depreciation note into a separate PR since this one can be merged immediately, the other one only aftersymfony/symfony#12237 gots merged.

/cc@webmozart

Thanks for the new PR. However, doesn't it make sense to mention in thecascade_validation section that in most cases, you should better use theValid constraint?

It is mentioned? "Instead, use theValid constraint in your model to cascade validation"

Hm, yeah, but it will then only be shown in the 2.6 version of the documentation. Though, as far as I understand the issue, these implications are also true for older versions, aren't they?

I added the recommendation to both PR's so it will appear in all versions. It was mentioned before but not recommended so I thought best would be to have it in a tip section.

I added one small suggestion. But after that, this has a 👍 from me! Furthermore, I'm very happy to have this clarified - iirc, the cascading worked differently in 2.0, so there was some "baggage" in understanding how this worked and documenting it absolutely correctly.

Thanks!

Just updated it as suggested.

Thanks Peter!