Repository navigation
Reject an association to an entity not exposed in the group - #311
Merged
TomHAnderson merged 1 commit intoOct 2, 2026
Merged
TomHAnderson merged 1 commit into
TomHAnderson merged 1 commit into
Conversation
An #[Association] to an entity with no #[Entity] attribute of the group failed every query of its entity's type, even one which did not ask for the association, with an error naming only the entity it refers to. It now throws Exception\Metadata naming the association when the metadata is built. The check runs after the metadata.build event, so a listener may add the entity, and removing one another refers to is an error. The check of a computed field of an entity type moves after the event with it. Two test groups had such an association, on entities their tests never query; their targets are now exposed in those groups. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## 14.0.x #311 +/- ##
===========================================
Coverage 100.00% 100.00%
- Complexity 1142 1147 +5
===========================================
Files 79 79
Lines 3088 3100 +12
===========================================
+ Hits 3088 3100 +12 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or 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
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.
An #[Association] to an entity with no #[Entity] attribute of the group failed every query of its entity's type, even one which did not ask for the association, with an error naming only the entity it refers to. It now throws Exception\Metadata naming the association when the metadata is built.
The check runs after the metadata.build event, so a listener may add the entity, and removing one another refers to is an error. The check of a computed field of an entity type moves after the event with it.
Two test groups had such an association, on entities their tests never query; their targets are now exposed in those groups.