-
Notifications
You must be signed in to change notification settings - Fork 473
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
Add insert, update, delete restrictions #1770
base: master
Are you sure you want to change the base?
Conversation
I don’t know why the build fails. I don’t have access to check the log. It builds successfully on my local branch. |
it seems the TestPublicApi failed, please update that in both projects. |
Sorry about that. Resolved. |
@bdebaere Thanks a lot for your contribution. However, what i am thinking is that "do we need to build these functionality in Web API OData? Should be these at use side? " And it seems Capabilities changes a lot, see https://github.com/oasis-tcs/odata-vocabularies/blob/master/vocabularies/Org.OData.Capabilities.V1.md. |
@bdebaere It seems it's better to add such extension methods into OData.Edm library and use OData model builder pattern to call those extension methods. |
Would really like to see this functionality added at the right level, and using the latest OASIS vocabulary. |
Add insert, update, delete restrictions based on https://www.odata.org/blog/introducing-a-capabilities-vocabulary/. It is now possible to call IsNotInsertable(), IsNotUpdatable(), IsNotDeletable() on the NavigationSourceConfiguration and NavigationSourceConfiguration. It is now also possible to call IsNotInsertable(), IsNotUpdatable(), IsNotDeletable() on the PropertyConfiguration. This results in additional annotations added where necessary.