You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So update_on is the parameter we are supposed to use. It is optional and set to [] so that the grid never updates.
update_mode is deprecated and optional but the default is GridUpdateMode.MODEL_CHANGED which is equivalent to VALUE_CHANGED | SELECTION_CHANGED | FILTERING_CHANGED | SORTING_CHANGED.
Since update_mode is still parsed, it will then set update_on=[ "cellValueChanged","selectionChanged","filterChanged","sortChanged"] which is not expected and I suspect unintended since update_on=[] by default. Even if you specify update_on with custom values, these will be added.
I think that update_mode should be set to None by default so that the default behaviour is the same as update_on. Then users can use either.
As a workaround for now, ensure that both update_on and update_mode reflect the same behaviour.
The text was updated successfully, but these errors were encountered:
@gregd33 Thank you so much for posting this issue and understanding what was happening. This was a very frustrating behavior in my application and it wasn't apparent to me that it was being caused by the streamlit-aggrid components.
So
update_on
is the parameter we are supposed to use. It is optional and set to[]
so that the grid never updates.update_mode
is deprecated and optional but the default isGridUpdateMode.MODEL_CHANGED
which is equivalent toVALUE_CHANGED | SELECTION_CHANGED | FILTERING_CHANGED | SORTING_CHANGED
.Since
update_mode
is still parsed, it will then setupdate_on=[ "cellValueChanged","selectionChanged","filterChanged","sortChanged"]
which is not expected and I suspect unintended sinceupdate_on=[]
by default. Even if you specifyupdate_on
with custom values, these will be added.I think that
update_mode
should be set toNone
by default so that the default behaviour is the same asupdate_on
. Then users can use either.As a workaround for now, ensure that both
update_on
andupdate_mode
reflect the same behaviour.The text was updated successfully, but these errors were encountered: