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

Allow navigations to owned types to be non-virtual #20015

Merged
merged 8 commits into from
Feb 27, 2020

Conversation

lajones
Copy link
Contributor

@lajones lajones commented Feb 21, 2020

Fix for #12462. Also a workaround for #19847 - which could now be solved by making the reference to the owned type non-virtual.

Added some tests.

AndriySvyryd
AndriySvyryd previously approved these changes Feb 21, 2020
Copy link
Member

@AndriySvyryd AndriySvyryd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

smitpatel
smitpatel previously approved these changes Feb 21, 2020
@lajones lajones changed the title WIP: Allow navigations to owned types to be non-virtual Allow navigations to owned types to be non-virtual Feb 21, 2020
@lajones
Copy link
Contributor Author

lajones commented Feb 21, 2020

@ajcvickers @AndriySvyryd @smitpatel Note: with the commits above the scenario in #19847 works even if the collection is virtual. Also I've added some tests including some to test non-proxy lazy-loading.

@AndriySvyryd AndriySvyryd self-requested a review February 22, 2020 01:24
@smitpatel smitpatel dismissed stale reviews from AndriySvyryd and themself February 22, 2020 01:28

Pending design meeting

@lajones
Copy link
Contributor Author

lajones commented Feb 26, 2020

@smitpatel @AndriySvyryd Reverted to original method of doing this as agreed. Please sign-off on that.

@lajones
Copy link
Contributor Author

lajones commented Feb 27, 2020

Pinging @smitpatel Any comments or is this what you were expecting?

@lajones lajones merged commit 233856f into master Feb 27, 2020
@lajones lajones deleted the 20200220_Issue12462_02 branch February 27, 2020 00:56
@AcidPat
Copy link

AcidPat commented Mar 25, 2020

What is the planned release for this - would love to see this in 3.1.4 as there is no work-around...

@ajcvickers
Copy link
Member

@AcidPat This is tracked by issue #12462. That issue is in the 5.0 preview 2 milestone, indicating that that is the release this will be included in. The workaround is to make the properties virtual.

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.

5 participants