view.totalPages becomes 1 when current page is out of bounds

[donaldgray]

The totalPages of a hydra view object would previously always show a number of pages in a collection according to the pageSize value.

It appears that this has changed - if the current page is "out of bounds" (e.g there's 10 pages but the page query parameter in the URL is 11) it will be set to 1.

How should this be handled?

Note by @griffri 24/10/2024 - totalItems is also set to 0 when the current page is out of bounds.

[p-kaczynski]

Personally I view a request with page out of bounds as a 400 Bad Request. That might be heavy handed, but makes the issue go away, as there would be no response body. For an API user this should be acceptable, for an UI this should not happen in the first place naturally, and is within the UI's wheelhouse to make a correct request instead, e.g. defaulting to page=1.