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.
I'm enabling sorting on the time table visualization. Instead of just passing the component to row, I'm passing an object with the component to be displayed as well as the underlying data. Sending the data as value to
Td
allows reactable to sort by the data instead of the component that's getting displayed.By default it will sort by the first column in fd.column_collection and then users can toggle sort for any of the columns.
I noticed a few issues with reactable, created an issue here. If the user changes the first column (to adjust the sort), reactable doesn't correctly resort until the page is reloaded (or the columns are manually sorted). This will be an issue for anyone creating the charts but for those using them it should look fine.
To sort the sparklines, I'm using the last value in the sparkline chart. Open to suggestions if you think there's a better way to sort this.