Closed AARON-CLARK closed 1 year ago
@tdwils, I played around in the app for a while and was not able to reproduce. Can you tell us a specific action in the app to generate one of these errors. I'm using the current devel
branch, which has the following pkg versions:
I will also like to add that a lot of these were occurring during the table generation. The newly added tryCatch()
with validate()
makes them disappear. You can see it in the screen shot with render_gt
.
Yes, they were occurring in the TG. I tried it just now, and the messages are gone.
Great! I will close this issue for now. Going forward, if new messaging/warnings/errors pop up, try to get rid of them and if it's persistent, create a new issue for that specific scenario.
Item 4 (latest versions of all packages)
A lot more messages are getting printed to the console when the app is run:
Regarding Item 4, I think this is a change coming from
shiny
version 1.7.2. That version has this change:It has made the stack trace more verbose. I tested this by using the lock file from the
devel
branch and updating onlyshiny
to v1.7.2. The additional messages appeared in the console when an error was forced.In
run_dev.R
we already haveoptions(shiny.fullstacktrace = FALSE)
, but it doesn’t seem to affect these messages.Maybe someone else can look at it so see if there is a way to go back to the less verbose version.