[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-961) 10.10 Projected Expanded Entity - be more explicit in combined $select/$expand cases
[ https://issues.oasis-open.org/browse/ODATA-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63127#comment-63127 ] Michael Pizzo edited comment on ODATA-961 at 8/9/16 6:19 PM: ------------------------------------------------------------- Had to read through this a bit and go through past versions of the doc to see how this evolved... Wording was changed in Draft 30, and the example was updated in Draft 41. I believe the intent is to differentiate between a selected nav link and an expanded nav property. the former appears without trailing parens, the later with trailing parens whether there is a subselect of properties or not (in the later case, the parens are empty). This clearly needs to be clarified... was (Author: mikep): Why do we duplicate the nav prop in the context url? seems like unclear wording in 10.9 and a bug in the 10.9 example to me. > 10.10 Projected Expanded Entity - be more explicit in combined $select/$expand cases > ------------------------------------------------------------------------------------ > > Key: ODATA-961 > URL: https://issues.oasis-open.org/browse/ODATA-961 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Bug > Components: OData Protocol > Affects Versions: V4.0_ERRATA03 > Reporter: Ralf Handl > Fix For: V4.01_WD01, V4.0_ERRATA04 > > > 10.9 describes that a navigation property appears twice in the context URL if it is specified in $select as well as in $expand with a nested $select. The text is somewhat vague, but one of the examples > 10.10 doesn't repeat that (almost) explicit statement, and also lacks a corresponding example -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]