-
Notifications
You must be signed in to change notification settings - Fork 97
Open
Description
We made an unwanted breaking change in SetSortExpression.
In DotVVM 4.3, changing the sort expression resets the paging to the first page.
In DotVVM 5.0, we moved the method to SortingOptions so it does not have access to paging. I think this is a problem, especially when using paging based on continuation tokens - it may stop working completely because the sort order is somehow embedded in the token payload, or we may just start from a completely random record.
I was thinking about adding the Changed event to the ISortingOptions so the dataset can hook on it and reset the pager (if it supports that). Or is there another way around?
Metadata
Metadata
Assignees
Labels
No labels