Thanks for an interesting presentation. But to me, using modules is more like learning to fly by radar. Debugging is harder, I need to add (and later delete) a "browser()" command rather than just clicking in the margin of RStudio to add a breakpoint. And I can't reload the app if I've changed the module code, I need to close the app and restart. I'm also a fan of "uiOutput()", which means extra steps in the server module as well. My recommendation would be to learn regular Shiny, then graduate to modules. Modules have advantages but as a second step, not for starting Shiny developers.
My approach is to create a mod_mymodule_apptest() where I wrap mod_mymodule_ui() and mod_mymodule_server() to test it on the fly. But I agree on the "vanilla shiny" first learning
This was fantastic. Thanks!
Thanks for an interesting presentation. But to me, using modules is more like learning to fly by radar. Debugging is harder, I need to add (and later delete) a "browser()" command rather than just clicking in the margin of RStudio to add a breakpoint. And I can't reload the app if I've changed the module code, I need to close the app and restart. I'm also a fan of "uiOutput()", which means extra steps in the server module as well.
My recommendation would be to learn regular Shiny, then graduate to modules. Modules have advantages but as a second step, not for starting Shiny developers.
My approach is to create a mod_mymodule_apptest() where I wrap mod_mymodule_ui() and mod_mymodule_server() to test it on the fly. But I agree on the "vanilla shiny" first learning
A better microphone would improve this presentation greatly.