Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stop using similar-looking owned entity in deeply nested case #16946

Merged
merged 1 commit into from
Aug 5, 2019

Conversation

ajcvickers
Copy link
Contributor

Fixes #15839

The issue was that both the immediate owner for Rejection.FirstTest#FirstTest.Tester#SpecialistStaff and Attitude.FirstTest#FirstTest.Tester#SpecialistStaff are the same resulting in the former being mistaken for the latter. The fix is to use the type rather than its name.

@ajcvickers ajcvickers requested a review from AndriySvyryd August 4, 2019 22:04
Fixes #15839

The issue was that both the immediate owner for `Rejection.FirstTest#FirstTest.Tester#SpecialistStaff` and `Attitude.FirstTest#FirstTest.Tester#SpecialistStaff` are the same resulting in the former being mistaken for the latter. The fix is to use the type rather than its name.
@ajcvickers ajcvickers force-pushed the ThisIsNotATpsReport0731 branch from 0cfd84c to 1828f38 Compare August 5, 2019 14:10
@ajcvickers ajcvickers merged commit f0c8b01 into release/3.0 Aug 5, 2019
@ghost ghost deleted the ThisIsNotATpsReport0731 branch August 5, 2019 14:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Using a deep Owned Entity graph raises exception
2 participants