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
Describe the bug
I went through the shiny app with one dataset, and then went to the first page to try another dataset in the same session. The second dataset loaded fine into the app, and the flagging table loaded fine, but the switches no longer changed the summary removed/retained when turned on/off, and I believe was no longer affecting the tadat$removals or some other reactive object. I am wondering if this is due to the unpredictable behavior of observes within observers, which occurs in the observeEvent function in the flagging module.
To Reproduce
Steps to reproduce the behavior:
Load one test dataset, and run flagging functions
Load second test dataset, re-run flagging functions
Switch on an off switch with results affected and look at summary table
Expected behavior
The flagging table should be responsive to multiple datasets in one session.
The text was updated successfully, but these errors were encountered:
I think it is fine to address this issue by simply adding a warning or text on the import tab to tell users that they must reload the shiny app before starting to work with a new dataset.
Describe the bug
I went through the shiny app with one dataset, and then went to the first page to try another dataset in the same session. The second dataset loaded fine into the app, and the flagging table loaded fine, but the switches no longer changed the summary removed/retained when turned on/off, and I believe was no longer affecting the tadat$removals or some other reactive object. I am wondering if this is due to the unpredictable behavior of observes within observers, which occurs in the observeEvent function in the flagging module.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The flagging table should be responsive to multiple datasets in one session.
The text was updated successfully, but these errors were encountered: