Fix Pagination Issue on Voters Dialogue

Currently on the Voters Dialogue accessed from witnesses >> Voters :

1. Clicking on >> does not take you to last page neither << takes to first page

added To Do label

assigned to @delrifai

removed To Do label

assigned to @mcfarhat and unassigned @delrifai

assigned to @delrifai and unassigned @mcfarhat

added To Do label

removed To Do label

added Doing label

The pagination issues are also happening under comments search. To reproduce:

1. Go to home page
2. Navigate to comment search section
3. Search based on account name and permlink (Example: actifit,actifit-updates--actifit-android-v0121-out)
4. Click on first page and last page

The pagination issues are also happening under account search. To reproduce :

1. Go to the home page
2. Navigate to the account search section
3. Search based on the account name and select all operations
4. Click on the first page and last page to check the behavior

mentioned in commit becfc825

mentioned in commit a7fdc254

@mcfarhat This is awaiting the results of our discussion about how the pagination should appear mirrored and where it should not.

I have also a couple of questions :

1. In Voters History:
   1. The pagination will never appear on this dialogue because of the conditions applied on pagination line 185 {votesHistory && votesHistory?.votes_history?.length > PAGE_SIZE && ( where votesHistory?.votes_history?.length is not reachable and should be votesHistory?.votes_history?.length
   2. The limit in the hook \hooks\api\common\useWitnessVotesHistory.ts is set to 100 which makes it the same as page size and hence no pagination will appear
   3. For this page, another ticket will be opened based on @mcfarhat 's feedback. Should we increase the limit here and allow paginating results?
   4. Please suggest the expected result, noting that https://hafbe.openhive.network/#/Witnesses/hafbe_endpoints.get_witness_votes_history allows increasing the limit
2. In block page pages\block[blockId].tsx :
   1. Pagination is working as expected but will not appear unless the block has more than 2000 operations
   2. Per the config file blockPagePaginationSize.There is a comment there // Temporary 2000 until cache problem solved.
   3. Let me know if we need further action here. Maybe limit the blockPagePaginationSize config to 100, or have feedback if the cache issue is fixed or not.

assigned to @mcfarhat and unassigned @delrifai

added discussion label

@mcfarhat Also please confirm if we need to show pagination when we only have one page. As it is currently working like that across the whole explorer

@ABW @jlachor would appreciate your feedback as to why the pagination is currently rendered in this mirrored mode.

As we are doing several fixes to pagination, we want to make it coherent across the app, but also more user-friendly if possible.

So if there is a reason why the mirrored mode is useful, we are happy to keep it and use it all across, otherwise, we will switch to the standard mode alongside making improvements and fixes to the pagination layout across the app.

Hello @mcfarhat , any updates on the above?

hey @delrifai , let us proceed to adjust our block explorer implementation so as we avoid mirrored implementation of pagination and use the traditional sense (1, 2...) instead of (last, ... 1)

Also let us make sure as you highlighted that first, last buttons work as intended, and we have a unified pagination experience across block explorer

unassigned @mcfarhat