[PR] Add support for Segment as Path from Odata v4.01 [olingo-odata4]

["joerattazzi-microsoft (via GitHub)" <gi...@apache.org>]

joerattazzi-microsoft opened a new pull request, #168:
URL: https://github.com/apache/olingo-odata4/pull/168

   Related Ticket: https://issues.apache.org/jira/browse/OLINGO-1630
   
   ### Summary
   Introduced in OData v4.01, OData supports "Key as Segment": https://www.odata.org/blog/OData-401-Committee-Spec-Published/
   
   > Key as Segment – Common semantics for representing keys within a URL as a segment, rather than enclosed in parenthesis.
   
   It appears to work fine from the client-side, but the server-side implementation is missing. In this proposal, we suggest adding optional support for the Key as Segment capability to CsdlEntitySet through `setKeyAsSegmentAllowed`. The goal was to add support but make it an opt-in feature to prevent breaking existing implementations.
   
    
   
   #### Link to specification:
   
   https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part2-url-conventions.html#_Toc31360937 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@olingo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] Add support for Segment as Path from Odata v4.01 [olingo-odata4]

["mibo (via GitHub)" <gi...@apache.org>]

mibo merged PR #168:
URL: https://github.com/apache/olingo-odata4/pull/168


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@olingo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org