Title: Add delayed response/debouncing for table filtering · Issue #87 · plotly/dash-table-experiments · GitHub
Open Graph Title: Add delayed response/debouncing for table filtering · Issue #87 · plotly/dash-table-experiments
X Title: Add delayed response/debouncing for table filtering · Issue #87 · plotly/dash-table-experiments
Description: Scenario I have a table with ~100-1000 rows of data, with filterable=True, and plots being rendered based on the visible rows in the table -- in full about ~10-50MB. When filtering, say, a percentage column, I toggle the Filter Rows butt...
Open Graph Description: Scenario I have a table with ~100-1000 rows of data, with filterable=True, and plots being rendered based on the visible rows in the table -- in full about ~10-50MB. When filtering, say, a percenta...
X Description: Scenario I have a table with ~100-1000 rows of data, with filterable=True, and plots being rendered based on the visible rows in the table -- in full about ~10-50MB. When filtering, say, a percenta...
Opengraph URL: https://github.com/plotly/dash-table-experiments/issues/87
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Add delayed response/debouncing for table filtering","articleBody":"### Scenario\r\n\r\n- I have a table with ~100-1000 rows of data, with `filterable=True`, and plots being rendered based on the visible rows in the table -- in full about ~10-50MB.\r\n- When filtering, say, a percentage column, I toggle the Filter Rows button, and begin typing my query for values of: `\u003e90.5`.\r\n- Dash issues a state-change and callback for each character, resulting in new figures being sent for `\u003e`, `\u003e9`, `\u003e90`, `\u003e90.`, and `\u003e90.5`, sending the entire set of figures and data each time.\r\n- Sometimes, this means that my desired filtering never actually gets applied since my app gets stuck handling the previous 4 callbacks.\r\n- This is also a large waste of bandwidth\r\n\r\n### Ideal outcome\r\n\r\n- I would like a `debounce` option for the `DataTable` class\r\n- The `debounce` option would prevent state-update from filtering rows by either:\r\n - a predefined duration (i.e. 500ms), or\r\n - a user specified amount of time\r\n- This would prevent multiple callbacks from being triggered during typing, resulting in meaningless or undesired updates\r\n- The `debounce` option could default to `False`, so that the standard behaviour is still live-updating, for people who would prefer that for their application.\r\n\r\n\r\nI'm not a javascript developer (Python, mostly), but will begin to try and tackle this in `src/components/DataTable.react.js` if there are no developers that can prioritize it. Is there another file/place that I'll need to update (other than the `usage.py` demonstrating the feature)?\r\n\r\nThanks!\r\nG","author":{"url":"https://github.com/gkiar","@type":"Person","name":"gkiar"},"datePublished":"2018-08-29T16:51:08.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/87/dash-table-experiments/issues/87"}
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:1289df28-9012-7f79-4295-63fa242c888e |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | 84CC:29EF90:119B466:17A8614:6A5D0EE8 |
| html-safe-nonce | 5f161cfb47499e39d1f8d976c87d2f2ed7ffeb7ea459e2dc58181f8718fd9348 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI4NENDOjI5RUY5MDoxMTlCNDY2OjE3QTg2MTQ6NkE1RDBFRTgiLCJ2aXNpdG9yX2lkIjoiMjU4MDYxODQwNTY2Mjc1NjU4NCIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 0099e142c136de0c8e1e976404578c0aa0f0e88bbba02b175752e232a9e2dbce |
| hovercard-subject-tag | issue:355247314 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/plotly/dash-table-experiments/87/issue_layout |
| twitter:image | https://opengraph.githubassets.com/5efbe1ac07e8c43cffc5e41d73582ad760e1b423b06f5de0a6557c883e3133be/plotly/dash-table-experiments/issues/87 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/5efbe1ac07e8c43cffc5e41d73582ad760e1b423b06f5de0a6557c883e3133be/plotly/dash-table-experiments/issues/87 |
| og:image:alt | Scenario I have a table with ~100-1000 rows of data, with filterable=True, and plots being rendered based on the visible rows in the table -- in full about ~10-50MB. When filtering, say, a percenta... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | gkiar |
| hostname | github.com |
| expected-hostname | github.com |
| None | 5290d7e14309ad1e76106a9c4237bd1041517e83ea182c8ab756752cb0c6940b |
| turbo-cache-control | no-preview |
| go-import | github.com/plotly/dash-table-experiments git https://github.com/plotly/dash-table-experiments.git |
| octolytics-dimension-user_id | 5997976 |
| octolytics-dimension-user_login | plotly |
| octolytics-dimension-repository_id | 99643060 |
| octolytics-dimension-repository_nwo | plotly/dash-table-experiments |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 99643060 |
| octolytics-dimension-repository_network_root_nwo | plotly/dash-table-experiments |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 9c975978430e9ad293956f2bbdaf153b1bd84a99 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width