Enable User Column Filters

[kmcentush]

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 and getFilterModel functions. On instantiation (or whenever the AgGrid Streamlit component key changes), these column filters can be applied automatically for the user. After the user filters the data, their filters can be accessed through the new column_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 the cast_to_serializable function. That is unrelated to the specific use case here, but I did encounter it while making this PR.

[kmcentush]

@PablocFonseca other than resolving the merge conflicts, is there anything else you would want before merging this PR?

[laky55555]

Hi @kmcentush,
Do you think adding the feature of retrieving current filters would be easy to add?
The use case would be to persist the same filters after the underlying data changes.

[kmcentush]

Hi @laky55555, that's more or less what I did by making these tweaks to the source. You can keep the filters in the streamlit state and apply it whenever the data changes, etc.

Here's the branch I was using in my own setup: https://github.com/cuberg-inc/streamlit-aggrid/commits/feat/col_filters

[devpedrorocha]

Hi guys,

I really appreciate what you did, @kmcentush. However, I want to know if you managed to set the initial value for the filters. I'm facing a problem where I want to set the filters before Ag-Grid is mounted. I tried setting the "filterModel" attribute in gridOptions, but it didn't work. This is how it looks:

[kmcentush]

I recall working around it some way by setting the filters before causing a streamlit refresh immediately after first load.

My team and I moved away from AggGrid more than a year ago, so unfortunately the code is buried in our commit history. That being said, if it seems like the filters work after initial mounting/on refresh, I think the brute-force strategy will work (albeit but not elegantly)

[devpedrorocha]

Thanks for answering @kmcentush, for curiosity, you and your team moved from Aggrid to what?

[kmcentush]

@devpedrorocha Our Aggrid use cases were replaced with Looker, as we mainly were using Streamlit for BI cases. The few places we still use Streamlit are for the much more dynamic interactions, but we've achieved those with Streamlit's own built in widgets, etc.