Update CollectionField.rst file for better documentation (adding extra considerations for its implementation) #6311
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding some extra considerations in the docs to use CollectionField class, since this class uses "add" & "remove" methods related to the Collection property from the entity that owns the collection in order to add and delete binded values; there is no documentation that explains that Collections must implement these methods and it is not intuitive so it would be a great help for anyone who is implementing this class for the first time (as it was in my case, after finding the solution 4 hours later).
References: https://stackoverflow.com/questions/48304399/q-symfony4-easyadmin-onetomany-not-saving-in-db