You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
There is often a * added by CSS used in order to tell if a field is required or not.
When I use a CollectionType, I do not want this * since adding a row to the collection is not required
The * could be considered more like telling that at least one row should be added.
But if I use required => false on the CollectionType, I lose the required attribute on all the children
Become
And I'm looking for
As explained in Follow up of #39943
It's a general rule for Form and child, but it seems weird for Collection.
Maybe the rule issue is with the required attribute of a CollectionType.
To me, it does not have a lot of sens, what is a required CollectionType vs a non required CollectionType ?
Both will submit a collection.
spackmat, Lionel-D, Andrew-Staves-Activ and RafaelKr