feat: re-routing latest page have items

[TonyDo99]

Re-routing get the latest page that has items with the option routingLatest

Description

• I found that we do not have the option to check and get the latest page has items. Let's give one scenario like this. At the front-end team, we do have 72082 pages and ten items per page, a total of 720821 items exist on the database. Suddenly one item is deleted by someone right at the moment another clicks to the latest page it probably returns empty items and the mismatch total page was calculated.

Example UI pagination

Result without option routingLatest

After re-routing with option routingLatest

• It auto return the latest page have items

Affected areas

modified: src/tests/paginate-raw-and-entities.spec.ts
modified: src/tests/paginate-raw.spec.ts
modified: src/tests/paginate.query.builder.spec.ts
modified: src/interfaces/index.ts
modified: src/paginate.ts

Test coverage

[TonyDo99]

Hi @bashleigh. Could you take a look at this feature?

[bashleigh]

Hi Tony, I think I understand the requirement of the feature however I feel this would include too many changes for the existing functionality. Is there a method we could do to avoid introducing too many changes to the existing methods? The wording also confuses me a little, routing latest, I can see you're trying to recalculate the pagination query to avoid a sort of 'race condition' scenario with deletions of already paginated items. Would you mind explaining how the math works?

https://github.com/nestjsx/nestjs-typeorm-paginate/pull/916/files#diff-c58e144dadf00250381ed55e6ce83245cda76aca84131ad494fd4911932f656fR74-R77

[TonyDo99]

Thank you for your reply @bashleigh. Take the example of 103 records that exist on the database. We need to paginate 10 items per page, then it will have 11 pages. The API call selects the page at 15, and the mathematics is used to recalculate the latest page that will have an item.

Example:
`page` - API selected
`limit` - API selected
`total` -  count total from queries

page = total / Number(limit) < Number(page)
         |            |              |
page =  103  /       10      <       15
  
page = Math.ceil(10.3) - ( it will return the page, the latest has an item mean page at 11 ) 

-- Otherwise it returns the page from the API selected

[TonyDo99]

I also tried to separate the feature, but currently I have not thought of a radical solution. I have applied this custom to my project, and it still works smoothly. I believe this feature should have when we use pagination