- 
                Notifications
    You must be signed in to change notification settings 
- Fork 64
Add support for PUT operation on entity sets and navigation properties based on UpdateMethod annotation #166
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 support for PUT operation on entity sets and navigation properties based on UpdateMethod annotation #166
Conversation
bcd3569    to
    df01079      
    Compare
  
    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.
I believe ComplexProperty cases need to be updated as well.
Also, it'd be good to have an example in trip service integration files.
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.
thanks for taking in the changes, one last thing.
ba5fdd5    to
    6c8395b      
    Compare
  
    | 
 @baywet thank you for review, please take another look. | 
6c8395b    to
    10e0007      
    Compare
  
    10e0007    to
    a57bff1      
    Compare
  
    use same base class
a57bff1    to
    045d631      
    Compare
  
    
Fixes #106
Fixes https://github.com/microsoftgraph/microsoft-graph-devx-api/issues/607
This PR adds support for PUT operations for entity sets , navigation properties and complex types based on the annotated Http method in the UpdateMethod property of Org.OData.Capabilities.V1.UpdateRestrictions annotation for a given target element.
See: https://github.com/oasis-tcs/odata-vocabularies/blob/053724df1ab5d19cc198f2a52cf8a85a2be08d79/vocabularies/Org.OData.Capabilities.V1.xml#L676-L677