Closed brownag closed 6 years ago
d98f41da911fd3cd0cb779a511e612a8062c5e00
Rather than trying to check version and fix package problems in the report itself... if there are problems with the packages the user is instructed to use update soilReports, run reportSetup() and reportUpdate() to update their packages and report.
Also, closes issues raised in #75 by adding check for illegal characters in output files and adding code to support (optional) user-specified output file names in config.R.
verify that file input and output paths are valid (before raster loading/sampling) and necessary packages are installed.
BONUS: also could check package VERSION (esp. for GitHub packages, which occasionally users overwrite with old CRAN versions or are out of date w.r.t bug fixes, namespace changes etc.).
Would/should we use our setup.R / report list version numbers or a commit hash code?