Implement pagination on the search page for users and badges from endpoints

[olamidepeterojo]

Implement pagination on the search page for users and badges from endpoints

---

Fixes #741

[gridhead]

Please follow the design language of the already implemented pagination areas.

Notice the arrow buttons at the bottom left side of the page on the accolade path.

[olamidepeterojo]

Yes i do, currently on it

[olamidepeterojo]

Hello @gridhead, I have done as instructed with an image attached below.
Secondly, I know ive been running tox -e docs before pushing commits and that reformats the code base but before pushing this commit I made sure not to run the command before pushing but I see 17 files changed which I find surprising because my previous commit had 1 change if im not mistaken. Kindly understand it was not in my intention to do so with the hopes of duplicate work to increase the likelihood of my selection

[gridhead]

@olamidepeterojo, you do realise that tox -e docs does not format the codebase but instead runs Sphinx to build the project's documentation from the docs/ directory, right? You would not have felt the need to run the tox -e docs commands or anything similar if you had gone through the workflow files or the testing configuration. The same learning would have helped you understand that maybe it is the tox -e format that you perhaps might have ended up running on the entire thing that resulted in changes across 17 files in total.

See, I understand that it is not your intention to be spammy across your pull requests, but it cannot be helped if you appear as one with your actual work. I have stated countless times that when we are reviewing your pull requests, we expect them to be in a ready state. It does not have to be polished or even functional, but it should give us an idea of how you approach a problem statement. From the representation that I get from your changes after my suggestions, it does not paint quite a favourable picture for you, if I were to be honest with you.

[olamidepeterojo]

@olamidepeterojo, you do realise that tox -e docs does not format the codebase but instead runs Sphinx to build the project's documentation from the docs/ directory, right? You would not have felt the need to run the tox -e docs commands or anything similar if you had gone through the workflow files or the testing configuration. The same learning would have helped you understand that maybe it is the tox -e format that you perhaps might have ended up running on the entire thing that resulted in changes across 17 files in total.

See, I understand that it is not your intention to be spammy across your pull requests, but it cannot be helped if you appear as one with your actual work. I have stated countless times that when we are reviewing your pull requests, we expect them to be in a ready state. It does not have to be polished or even functional, but it should give us an idea of how you approach a problem statement. From the representation that I get from your changes after my suggestions, it does not paint quite a favourable picture for you, if I were to be honest with you.

You’re right @gridhead , I misunderstood the purpose of the tox environments and ended up running formatting across the repository instead of limiting it to my changes. I have made sure to correct this

[gridhead]

Please limit the length of your commit messages to under 50 characters and sign your commit activities only once!

[olamidepeterojo]

Please limit the length of your commit messages to under 50 characters and sign your commit activities only once!

Done as Instructed