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
We could collect all importFrom material from the individual R/*.R files into R/firstlib.R (as in e.g. eurostat). This helps to manage all imports in a single place.
The text was updated successfully, but these errors were encountered:
For me, listing the imports in the Roxygen-docs just before the function definition helps to quickly find where specific imports are used. Then again I do (almost consistently) use package::function() format, which makes it slightly easier to find specific imports.
Since Roxygen2 collates the imports anyway, is there anything else to be managed (e.g. packages collisions etc)?
Not sure if this makes a big difference in practice. One benefit that I have noticed is that it is easy to see at once which packages are imported, and then keep the DESCRIPTION file imports up-to-date (also removing unnecessary packages).
We could collect all importFrom material from the individual R/*.R files into R/firstlib.R (as in e.g. eurostat). This helps to manage all imports in a single place.
The text was updated successfully, but these errors were encountered: