New SortAndPage operator

[RolandPheasant]

This is the following up to the SortAndVirtualize - see #888

If is an almost a direct lift of the code but using page based calculations. This is part of the drive to eliminate the Sort operator altogether, and subsequently the need to propagate the index on Change<TObject,TKey>.

Old

var pageRequests=new BehaviorSubject<IPageRequest>(new PageRequest(1, 25))

myCache 
  .Sort(myComparer)
  .Page(pageRequests)

New

var pageRequests=new BehaviorSubject<IPageRequest>(new PageRequest(1, 25))

myCache 
  .SortAndPage(myComparer, pageRequests)

There is a also a new Bind() overload to bind the results of the page response.

Additionally I have renamed SortAndBind which acts on a a virtual response to Bind() .

I just need and replace SortBy with SortByAndBind operator and I am happy to make the big version release.

[JakenVeina]

On a high-level note, am I correct in reading that Virtualize and Page are just the same thing? Is there any actual difference, other than the indexing parameters?

[JakenVeina]

Doesn't this filter out some valid requests? E.G. { Page: 0, Size: 10 }? Or is Page here 1-indexed?

[RolandPheasant]

It just ignores bad input. The other alternative would be just to throw an exception

[RolandPheasant]

Dang, I just re-read your comments. Page zero is not valid. Paging always starts at 1.

[RolandPheasant]

On a high-level note, am I correct in reading that Virtualize and Page are just the same thing? Is there any actual difference, other than the indexing parameters?

Indeed so. It's almost the same but I've replaced it because it already exists and we can bet our bottom dollar that someone is suing it in the wild.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.