You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I load devtools automatically in my R profile and always check my site rendering with build_site(). By default this wrapper suppresses output (quiet = TRUE). Unfortunately this means you can miss a lot of really useful warning information (particularly the new alt-text warnings that have been added).
As a lot of effort has gone in to the new pkgdown release, in particular the various warnings / information, it seems a shame for this to be hidden. Is it worth considering changing the default to quiet = FALSE?
The text was updated successfully, but these errors were encountered:
TBH it's news to me that devtools has a build_site() function! (I inherited this package as a very mature product.)
So as someone who does a lot of package dev and does actually maintain devtools, my local move for this is to use the pkgdown addin or, for more specialized tasks, make pkgdown::build_*() calls in the console. I realize that doesn't totally address your question, but maybe it's interesting to know.
@hadley As pkgdown maintainer and creator of devtools, do you have an opinion here?
I load devtools automatically in my R profile and always check my site rendering with
build_site()
. By default this wrapper suppresses output (quiet = TRUE
). Unfortunately this means you can miss a lot of really useful warning information (particularly the new alt-text warnings that have been added).As a lot of effort has gone in to the new pkgdown release, in particular the various warnings / information, it seems a shame for this to be hidden. Is it worth considering changing the default to
quiet = FALSE
?The text was updated successfully, but these errors were encountered: