feat: add CSV export to DataTable (fixes #1403)#1464
Open
tech00exploere wants to merge 1 commit into
Open
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
1 participant
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.
Description
This PR adds a CSV export feature to the DataTable component, allowing users to download the currently displayed table data as a CSV file with a single click.
It also includes a small ESLint configuration fix by renaming .eslintrc.js to .eslintrc.cjs to ensure compatibility with the current project setup.
Related Issues
Fixes #1403
Steps to Test
-> All rows are present
-> Data matches table content
Additional Verification :
->Ensure the button does nothing when the table is empty (no crash or download)
->No UI layout changes except the new button in the toolbar
UI Change
->A new "Export CSV" button is added in the DataTable header next to Refresh and Search controls.
Checklist
I have tested these changes
I have updated relevant documentation
I have ensured code is clean and readable
My changes generate no new warnings or errors
The pull request title is clear and descriptive