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
Im using streamlit, which uses the glide-data-grid. Since the upgrade to glide-data-grid v6.0.0 it seems that the dropdown cell is no longer rendering cell values that arent in the list of allowed values. This breaks a lot of my use cases for the dropdown cell:
I often want my users to be able to add strictly unique rows to a dataframe. For example, I have a list of parameter names that the users should be able to add and assign values to. I only want the users to be able to add a parameter name once, so they can only assign one value to this parameter. I therefore remove the values that are already added from the available options. Prior to v6.0.0 the values would still be rendered, eventhough they were no longer part of the available options. It seems that this has now changed:
I believe the changes here are whats causing this new behaviour.
Is there any way to get old bahviour back for this? Thanks!
The text was updated successfully, but these errors were encountered:
Hey guys,
Im using streamlit, which uses the glide-data-grid. Since the upgrade to glide-data-grid v6.0.0 it seems that the dropdown cell is no longer rendering cell values that arent in the list of allowed values. This breaks a lot of my use cases for the dropdown cell:
I often want my users to be able to add strictly unique rows to a dataframe. For example, I have a list of parameter names that the users should be able to add and assign values to. I only want the users to be able to add a parameter name once, so they can only assign one value to this parameter. I therefore remove the values that are already added from the available options. Prior to v6.0.0 the values would still be rendered, eventhough they were no longer part of the available options. It seems that this has now changed:
I believe the changes here are whats causing this new behaviour.
Is there any way to get old bahviour back for this? Thanks!
The text was updated successfully, but these errors were encountered: