Skip to content

v2.3.4 Introduce ResourceDefinition #330

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

Merged
merged 9 commits into from
Jul 5, 2018
Merged

v2.3.4 Introduce ResourceDefinition #330

merged 9 commits into from
Jul 5, 2018

Conversation

jaredcnance
Copy link
Contributor

Closes #297
Closes #321

// There are some scenarios, especially ones where users are using a different
// data model than view model, where they may use a repository implmentation
// that does not match the deserialized type. For now, we will continue to support
// this use case.
Copy link
Contributor Author

@jaredcnance jaredcnance Jul 5, 2018

Choose a reason for hiding this comment

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

Original release notes...saving for later. See the comment ☝️ for why this was not included.

We are now caching PropertyInfo when we build the ContextGraph so that we can reduce the amount of reflection performed per-request. Previously when setting attribute values during serialization, we would look up properties by name on the incoming type. This allowed sharing repository implementations for multiple types that may have common attribute names. However, this is incorrect behavior and it has been indirectly corrected through this performance improvement.

@jaredcnance jaredcnance changed the title Develop v2.3.4 Introduce ResourceDefinition Jul 5, 2018
@jaredcnance jaredcnance merged commit 271693a into master Jul 5, 2018
jaredcnance added a commit that referenced this pull request Aug 12, 2018
v2.3.4 Introduce ResourceDefinition
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant