Add export_button argument for dash datatable
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 24.4k
- Forks
- 2.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 13
Description
Hello All,
I am following up from the solution posted here:
https://community.plotly.com/t/moving-datatable-export-button-and-changing-text/39115
by Higgcz
I had a similar issue and will probably use this workaround solution. This does however make maintaining our dash app more nuanced, particularly when there is more than one datatable.
The request is to include export_button as an argument to datatable where the value is the id of a button that is in the layout.
The client side callbacks would be automatically built by dash and the default button would not be displayed.
In my application I am making use of the dash-bootstrap-components library; this feature would allow the styling and positioning of the export button to be abstracted away from the datatable at the uses choice.
Thanks.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked community workaround and reviewing the existing Dash DataTable export-button behavior. Trace how a layout button ID could connect to automatically generated client-side callbacks. Done means DataTable accepts an export_button argument, hides its default button, and supports exporting through the referenced layout button, including multiple tables.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-visualization, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100