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

Context Ulr select clause parsing is not per OData spec #1268

Closed
biaol-odata opened this Issue Oct 1, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@biaol-odata
Member

biaol-odata commented Oct 1, 2018

*According to OData ABNF rules for V4 and V4.01, context Url select clause is a comma separated list, while each item can be either a simple property or in the form of navigation property followed by parenthesized selected properties, such as (Id, User(FirstName, LastName)).
The parsing design & implementation currently handles it as simple form of comma separated list, and needs to be able to parse / represent nested form correctly. *

Assemblies affected

ODL 6.x, ODL 7.x

Reproduce steps

  • Select clause: (Id, User(FirstName, LastName)).*

Expected result

Top level should be parsed into two items: "Id", "User(FirstName, LastName)"

Actual result

Top level is incorrectly parsed into three items: "Id", "User(FirstName", "LastName)"

Additional detail

Optional, details of the root cause if known. Delete this section if you have no additional details to add.

@biaol-odata biaol-odata self-assigned this Oct 1, 2018

@biaol-odata biaol-odata added the feature label Oct 1, 2018

@biaol-odata

This comment has been minimized.

Member

biaol-odata commented Oct 1, 2018

This issue is another prerequisite for the $expand context url: OData/odata.net #1265

@biaol-odata

This comment has been minimized.

Member

biaol-odata commented Oct 23, 2018

PR #1286 has been merged. Issue can be closed as fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment