best dev practices without autoreload? #896
Description
Hi all, I'm wondering if anyone can share tips on how to best develop Shiny app using the golem framework while not being able to use autoreload. It seems like autoreload is so vital to Shiny development and not having it has made it hard for me to adopt golem - especially early on in projects when I am experimenting.
Do people just have insane discipline and stop + restart their app every time they make a small change, or do people opt for test-driven development? What about UI decisions - what is the best way to test small changes without accumulating 100 dead tabs in the browser?
Interested to hear any insights or a pointer to where I can read more about this. Thanks for the feedback!