You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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:
Note: the index in
$orderby
is evaluated on the implicit server-defined order of thecomponents
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.With that however it would be more "natural" to use a nested
$index
option instead of an index segment:Proposal
Two alternatives:
Imported from ODATA-1506
The text was updated successfully, but these errors were encountered: