Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch to using AG Grid for interactive table #127

Open
alyssadai opened this issue Jan 16, 2024 · 1 comment
Open

Switch to using AG Grid for interactive table #127

alyssadai opened this issue Jan 16, 2024 · 1 comment
Labels
_flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again refactor Simplifying or restructuring existing code or documentation.

Comments

@alyssadai
Copy link
Collaborator

We're gradually reaching the limit of what the native dash datatable can offer in terms of filtering capabilities and other features, and have already needed to code or investigate workarounds for e.g., multiple values selection, filtering for missing values.

These kinds of features are supported by default in Dash AG Grid, which offers significantly greater customization, (apparently) better performance, and overall seems like a more sustainable solution for a heavily interactive datatable. Based on a quick overview of community posts, it also seems like Dash AG Grid is being more actively maintained.

This issue will serve as a place to catch new feature requests that would require custom workarounds in dash datatable and so will not be fixed/implemented until after the migration:

Resources:

Copy link

github-actions bot commented Apr 1, 2024

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days.
We have applied the _flag:stale label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:

  • prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
  • close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
  • archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case
    apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this
    label in the future. Use sparingly!

@github-actions github-actions bot added the _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again label Apr 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
_flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again refactor Simplifying or restructuring existing code or documentation.
Projects
Status: No status
Development

No branches or pull requests

2 participants