### 📜 Description 1. Go to explore jobs and select any one filter. 2. Click on next button. 3. You will see page flickering from 1 to 2.. 2 to 1 ### 👟 Reproduction steps Method - 1 I was thinking of hiding prev / next button using if else based on currentPage and totalPages. Method - 2 Adding css to make it look like a disable button and not invoking setQueryParams(). ### 👍 Expected behavior It shouldn't flicker ### 👎 Actual Behavior with Screenshots https://github.com/user-attachments/assets/94aec105-5a23-46aa-b09f-4169cd62149c ### OS name Windows ### browser name Chrome ### npm version _No response_ ### node version _No response_ ### 📃 Provide any additional context for the Bug. _No response_ ### 👀 Have you spent some time to check if this bug has been raised before? - [X] I checked and didn't find a similar issue ### 🏢 Have you read the Contributing Guidelines? - [X] I have read the [Contributing Guidelines](https://github.com/code100x/job-board/blob/main/CONTRIBUTING.md) ### Are you willing to submit PR? Yes I am willing to submit a PR!
📜 Description
👟 Reproduction steps
Method - 1
I was thinking of hiding prev / next button using if else based on currentPage and totalPages.
Method - 2
Adding css to make it look like a disable button and not invoking setQueryParams().
👍 Expected behavior
It shouldn't flicker
👎 Actual Behavior with Screenshots
100xJobs.-.Google.Chrome.2024-11-04.20-06-17.mp4
OS name
Windows
browser name
Chrome
npm version
No response
node version
No response
📃 Provide any additional context for the Bug.
No response
👀 Have you spent some time to check if this bug has been raised before?
🏢 Have you read the Contributing Guidelines?
Are you willing to submit PR?
Yes I am willing to submit a PR!