-
Notifications
You must be signed in to change notification settings - Fork 62
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
RetrieveFunction and UpdateAction for aggregated entities #212
base: main
Are you sure you want to change the base?
Conversation
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.
It would be nice to have a matching JSON example of an aggregation result with instance annotations.
<Parameter Name="Updates" Type="SalesModel.Sale" Nullable="false"> | ||
<Annotation Term="Core.Description" String="Aggregate entity with nested properties that are to be updated, like the body of a PATCH request" /> | ||
</Parameter> | ||
<ReturnType Type="SalesModel.Sale" Nullable="false"> | ||
<Annotation Term="Core.Description" String="Aggregate entity with updates applied" /> | ||
</ReturnType> |
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.
Non-nullable properties that have been aggregated away will be absent in the parameter Updates
and in the return value. This is allowed by [OData-Aggr, section 3.1.1].
aggregation-cs03-release-candidate
…AP/odata-vocabularies.git into aggregation-cs03-release-candidate
Based on these data:
OData V2:
OData V4: