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
When the dependent field is not displayed, but is previously set, it should be nice to set it to null or a default value we want.
I don't really know if this can be implemented rirectly, or maybe, mentioned in the documentation to remind people implement it.
Yes... I haven't really thought about this. I guess, inside the form, if 'breakfast' !== $meal, the rating field will be removed... so the result would be that setRating() is never called... and so it would keep whatever value it had when the object was first passed to ->createForm() (i.e. the value set in the database).
Can you confirm that my statement above is accurate? If so, yes, my feeling is that this would be a good fit for the docs.
When the dependent field is not displayed, but is previously set, it should be nice to set it to null or a default value we want.
I don't really know if this can be implemented rirectly, or maybe, mentioned in the documentation to remind people implement it.
Eg:
The text was updated successfully, but these errors were encountered: