-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: dropdown_extra() keeps values in memory even if reactable source data changes #50
Comments
Seems to be linked to changes made here: 75d8f58 to keep input changes when using pagination. |
Trying to fix Appsilon#50
I second this. |
I have run into similar issue, you can force shinyjs::runjs("memory = {};") Additional note: in order to properly flush the values you will need to re-render the whole table (so |
I will give this suggestion a shot and keep my fingers crossed. I would be great if this issue was properly fixed however. My gut tells me that this should be a fairly easy fix. |
I can confirm that Here is a reprex.
Gravacao.de.tela.de.2025-02-06.11-52-51.webm |
Guidelines
Project Version
0.2.0
Platform and OS Version
No response
Existing Issues
No response
What happened?
if a value is changed using
dropdown_extra()
, then the value persist on the table even if the source data of my reactable changes.Steps to reproduce
Expected behavior
I was expecting these values to be "flushed" when the data changes.
Or maybe a mechanism to force the refresh
Attachments
Screenshots or Videos
Screen.Recording.2023-12-12.at.14.53.42.mov
In this example I changed the values "Type" to "Van" on the first 2 lines in df1.
When I switch to df2, the 2 first lines have a "Van" "Type" which is not the case in the dataset.
Additional Information
No response
The text was updated successfully, but these errors were encountered: