Open hadley opened 5 years ago
Funny enough, whenever I teach shiny, I always explicitly say how much I love that accessing a reactive outside of a reactive context is a great example of informative error messages, because it does actually tell you the problem.
Though I can see how .getReactiveEnvironment()$currentContext()
can be intimidating to newcomers, and I agree it would be helpful to see the name of the variable that was attempted to be accessed