Forbid ContainsXxx unmanaged data modification #1004
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mvorisek
force-pushed
the
fix_contains_hooks
branch
from
0143433 to
abd00b3
Compare
mvorisek
force-pushed
the
fix_contains_hooks
branch
from
abd00b3 to
4d88cef
Compare
mvorisek
changed the title
mvorisek
changed the title
mvorisek
commented
Jun 7, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
closes #881
we forbid the hidden feature to prevent unwanted behaviour (no hooks, normalization, ...)
when the direct unmanaged data modification is really wanted, simply add a field using
$m->addField()instead of$m->containsOne()(or$m->containsMany())