Conversation
mateacademy-ai-mentor
left a comment
mateacademy-ai-mentor
left a comment
There was a problem hiding this comment.
Review Summary
I am approving your solution. You've done a great job implementing the core pagination functionality, and all mandatory requirements have been met. The component logic is solid and the UI updates as expected. The main area for improvement is implementing the optional requirement to manage the pagination state using URL query parameters. In src/App.tsx, instead of static default values, you could use the useSearchParams hook from react-router-dom to initialize the state from the URL. This would make the page state shareable and persistent across reloads. Overall, this is a strong submission!
✨ Please rate this review in the Platform's notification center1. I will be grateful for your feedback! ✨
Footnotes
| const [currentPage, setCurrentPage] = useState<number>(1); | ||
| const [perPage, setPerPage] = useState<number>(5); |
There was a problem hiding this comment.
The state is initialized with static default values. According to the requirements, you should use React Router to get these values from the URL query parameters (?page=...&perPage=...) when the page loads.
2 participants
No description provided.