@mtojek can you be more specific? In this case, what is missing is the pagination widget right?

Yes, I can. The reason why we implemented the count on the backend side was so the frontend DOES NOT show the 404, but rather renders or goes to the last page.

What I can see here is just "Go to the first page", but the idea is to render the last available page.

Go to the last page would add one redirect and maybe unexpected IMO. What I see other apps doing is a not found error message, wdyt @mafredri ?

Here's how I think about it @BrunoQuaresma.

Imagine the following situation:

1. Pagination is 10 workspaces / page
2. There are 31 workspaces (4 pages)
3. User is on page 4
4. Someone deletes 11 workspaces
5. There are now only 20 workspaces (2 pages)
6. What happens to the user viewing page 4? Keep in mind we refresh workspaces list on such events

As a user, I would like for the pagination to contain [1] [2] [4] where 4 can be highlighted to signify it's selected (and maybe somehow indicate it doesn't exist). The workspace list would also show "no workspaces", similar to a search producing no results.

This way, I can easily recover and choose whether or not I want to go to the first or the last page (1 or 2). Given more pages it could look like [1] ... [10] [11] [12] ... [14] or something like that.

I think encountering a 404 in my described scenario would feel pretty weird and unexpected (since it used to he a page).

@mafredri I see that, I just think redirecting the user to the last page is not usual, at least in other apps, but I'm ok with showing the pagination.

Updated: