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.

Sign up for GitHub

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

Jump to bottom

When mapping to backing fields handle cases where field is on base type #758

Closed
ajcvickers opened this issue Oct 1, 2014 · 1 comment
Closed

When mapping to backing fields handle cases where field is on base type #758

ajcvickers opened this issue Oct 1, 2014 · 1 comment
Labels
closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-bug
Milestone
1.1.0

Comments

@ajcvickers
Copy link
Contributor

No description provided.

@rowanmiller rowanmiller added this to the 1.0.0-rc1 milestone Oct 10, 2014
@rowanmiller rowanmiller modified the milestones: Backlog, 1.0.0-rc1 Oct 10, 2014
@ajcvickers
Copy link
Contributor Author

This might already be done. If not, it is a bug and should be done in 1.1

@ajcvickers ajcvickers modified the milestones: 1.1.0, Backlog Jul 8, 2016
@ajcvickers ajcvickers self-assigned this Jul 8, 2016
ajcvickers added a commit that referenced this issue Jul 27, 2016
@ajcvickers
Add change tracker support for read-only properties with backing fields
6acd434 
Issue #4461

Previously the materializer would use the backing field, but then when a value needed to be set for fixup, etc, things would fall down. Now we generate delegates everywhere that can use the backing field.

Note that query still prefers the backing field, while fixup prefers the property.

MemberMapper was made a service of the model. Only the minimal done here--we can allow it to be set by convention or fluent API if the need to customize it is requested.

Also fixed #758 - When mapping to backing fields handle cases where field is on base type
ajcvickers added a commit that referenced this issue Jul 27, 2016
@ajcvickers
Add change tracker support for read-only properties with backing fields
7c54279 
Issue #4461

Previously the materializer would use the backing field, but then when a value needed to be set for fixup, etc, things would fall down. Now we generate delegates everywhere that can use the backing field.

Note that query still prefers the backing field, while fixup prefers the property.

MemberMapper was made a service of the model. Only the minimal done here--we can allow it to be set by convention or fluent API if the need to customize it is requested.

Also fixed #758 - When mapping to backing fields handle cases where field is on base type
@ajcvickers ajcvickers mentioned this issue Jul 27, 2016
Merged
ajcvickers added a commit that referenced this issue Jul 28, 2016
@ajcvickers
Add change tracker support for read-only properties with backing fields
0f3013e 
Issue #4461

Previously the materializer would use the backing field, but then when a value needed to be set for fixup, etc, things would fall down. Now we generate delegates everywhere that can use the backing field.

Note that query still prefers the backing field, while fixup prefers the property.

MemberMapper was made a service of the model. Only the minimal done here--we can allow it to be set by convention or fluent API if the need to customize it is requested.

Also fixed #758 - When mapping to backing fields handle cases where field is on base type
@ajcvickers ajcvickers added type-bug closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. labels Jul 28, 2016
@ajcvickers ajcvickers modified the milestones: 1.1.0-preview1, 1.1.0 Oct 15, 2022
@ajcvickers ajcvickers removed their assignment Sep 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-bug
Projects
None yet
Milestone
1.1.0
Development

No branches or pull requests
3 participants
@ajcvickers @rowanmiller @AndriySvyryd