Open soniamitchell opened 3 years ago
But devtools::check()
is a horror... and history has told us that despite working on this for many years, many students still didn't learn to spot global variables.
But it’s one of my favourite things in R 😆 Maybe we can relegate findGlobals()
to the console then? And add a bit to the functions lesson for troubleshooting? So it’s more active and less copy and pasting / using functions we give them?
I think again it'll be the assert_no_globals()
that we use instead... whether it's at the console or in a script is another question. By and large they don't seem to understand using the console!
I'd be tempted to use 'findGlobals()' rather than 'assert_no_globals()' given that the latter is part of the RPiR package, which isn't something they want to be "carrying" with them once the course ends.
As for using the console, I think we really need to talk to the intro to R course, or else include this type of stuff in the introductory lecture / exercises.
Remove findGlobals() from the course or relegate it to console use only.
devtools::check()
is far more comprehensive, and can be used to debug a package since provides warnings and errors.