Skip to content

Conversation

NewtonLC
Copy link

Checklist:

Closes #532

Worked in collaboration with @CarlyAThomas

In relation to post.

@NewtonLC NewtonLC requested a review from a team as a code owner January 25, 2025 00:02
Comment on lines +143 to +149
>
<option value={10}>10</option>
<option value={20}>20</option>
<option value={30}>30</option>
<option value={40}>40</option>
<option value={50}>50</option>
</select>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is there a reason why this is hardcoded to 50?

Comment on lines +160 to +170
<button
onClick={() => setPageIndex(0)}
disabled={!canPreviousPage}
style={{
marginLeft: '10px',
marginRight: '10px',
color: '#d1d1d1',
fontSize: '1.5em'
}}
>
|<b>&lt;</b>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see a lot of repeated styling code in the buttons, would we be able to cut down on this?


const startEntry = pageIndex * entriesPerPage + 1;
const endEntry = Math.min((pageIndex + 1) * entriesPerPage, rows.length);
const totalEntries = rows.length;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should leverage this variable for the pagination feature, we should be able to dynamically create the options for the footer, removing the hardcoded options. We can just generate some mock data to fill in the students in a class so that we can simulate the footer still displaying and working correctly? Let me know your thoughts on this.

@GuillermoFloresV
Copy link
Member

left some comments, let me know if I can clarify any of them!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Enhancements to the Admin dashboard page
2 participants