Add sorting and page size control to Supported Projects table#99
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📌 Summary
This PR introduces improvements to the Supported Projects table by adding column sorting and a configurable page size selector for pagination. These enhancements improve usability when working with larger sets of infrastructure projects.
✨ Features
🔃 Column Sorting
Users can now sort the Supported Projects table by:
Behavior
📄 Page Size Selector
A new control has been added to allow users to change the number of rows displayed per page.
Available options:
Behavior
🧠 Technical Details
Introduced unified state management for:
sortColumnsortDirectionpageSizecurrentPageEnsured correct interaction between:
Sorting implemented to support correct data types:
Ensured clean separation between UI and data handling logic
🧪 Testing
The following scenarios were verified manually:
🚀 Impact
This update improves: