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
We now retain properly the collection of orders by using accessor methods instead of relying on using the orders field. TypedSort orders are not using the orders field, instead they iterate over recorded persistent property paths.
Closes#2103
Original pull request: #2377.
We now retain properly the collection of orders by using accessor methods instead of relying on using the orders field. TypedSort orders are not using the orders field, instead they iterate over recorded persistent property paths.
Closes#2103
Original pull request: #2377.
hgarus opened DATACMNS-1704 and commented
This might me misunderstanding the API. I did try to sort by multiple properties doing the following:
The result is a Sort by property2, looking at the code the reason seems to be Sort.and() accessing Sort.orders directly, which is empty for TypedSort
No further details from DATACMNS-1704
The text was updated successfully, but these errors were encountered: