-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Labels
ABNFURL ConventionsURL ConventionsURL ConventionsV4.03Too vague or controversial for 4.02Too vague or controversial for 4.02
Description
OData already allows numeric index segments for ordered collections in the path part of the URL, see ODATA-820.
Allow this also in Path Expressions:
GET Entries?$expand=components($orderby=name))&$orderby=components/0/name
Note: the index in $orderby
is evaluated on the implicit server-defined order of the components
as $orderby
has to be evaluated before $expand
. This is somewhat counter-intuitive and could be remedied by further extending the path syntax to e.g.
$orderby=components($orderby=name)/0/name
With that however it would be more "natural" to use a nested $index
option instead of an index segment:
$orderby=components($orderby=name;$index=0)/name
Proposal
Two alternatives:
- ODATA-1506: Allow numeric index segment in path expressions odata-abnf#59
- ODATA-1506: allow indexing into a collection in a specific order odata-abnf#61
Imported from ODATA-1506
Metadata
Metadata
Assignees
Labels
ABNFURL ConventionsURL ConventionsURL ConventionsV4.03Too vague or controversial for 4.02Too vague or controversial for 4.02
Type
Projects
Status
No status