-
-
Notifications
You must be signed in to change notification settings - Fork 158
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
Conversation
feat(DocumentBuilder): allow for output attribute filtering
feat(csproj): add SourceLink
fix(AttrAttribute): unexpected scenarios cause breaking change
specify symbols server for develop
// 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. |
There was a problem hiding this comment.
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 theContextGraph
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.
v2.3.4 Introduce ResourceDefinition
Closes #297
Closes #321