Make error message suggestion accurate #9537
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
greg0ire
changed the title
greg0ire
reviewed
Feb 22, 2022
greg0ire
reviewed
Feb 22, 2022
kiler129
force-pushed
the
fix-bug-9536
branch
from
93f229e
to
ca35fe8
Compare
greg0ire
reviewed
Feb 22, 2022
Wrong validation message is displayed when an incorrect bidirectional bi-directional mapping is set up. When the owning side is configured correctly and the target side is missing the back reference, the ORM suggests adding inverseBy instead of mappedBy, with the field name missing. This commit fixes this problem.
kiler129
force-pushed
the
fix-bug-9536
branch
from
ca35fe8
to
79f73a2
Compare
greg0ire
approved these changes
Feb 22, 2022
|
Thanks @kiler129 ! |
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.
Wrong validation message is displayed when an incorrect bidirectional
one-to-one mapping is set up. When the owning side is configured
correctly and the target side is missing the back reference the ORM
suggests adding inverseBy instead of mappedBy, with the field name
missing.
Fixes #9536