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.
For my specific use case, there is a huge advantage to letting my users ultimately export their current column filters and later re-upload them. This can shortcut a lot of manual filtering if the user does pretty routine analysis.
This pull request exposes the ability to both read/write the column filters through the Ag-Grid enterprise
setFilterModel
andgetFilterModel
functions. On instantiation (or whenever the AgGrid Streamlit componentkey
changes), these column filters can be applied automatically for the user. After the user filters the data, their filters can be accessed through the newcolumn_filters
field in the component value/response.Please let me know if you have any questions. Happy to create a minimal Streamlit example if my use case is not clear.
Edit: I also fixed a bug in the
text_columns
aspect of thecast_to_serializable
function. That is unrelated to the specific use case here, but I did encounter it while making this PR.