This is important because, as in the model and package developed for a client, a package may be used to run lots of the generic code (which can make up a high proportion of the model) and then what is left for the model visualisation is actually a smaller subset of model code.
Potential fix:
renv::dependencies() provides a table of dependencies by file path.
We can adapt and run by function! This will give external dependency list for each function.
Then, for set functions we could load the arguments and body. It won't be possible to load the full code with Roxygen because this may be stored somewhere else.
Note: we won't always want full function by function dependencies as this will be massive, in most cases we will just want a list of packages used.
This is important because, as in the model and package developed for a client, a package may be used to run lots of the generic code (which can make up a high proportion of the model) and then what is left for the model visualisation is actually a smaller subset of model code.
Potential fix:
renv::dependencies()provides a table of dependencies by file path.We can adapt and run by function! This will give external dependency list for each function.
Then, for set functions we could load the arguments and body. It won't be possible to load the full code with Roxygen because this may be stored somewhere else.
Note: we won't always want full function by function dependencies as this will be massive, in most cases we will just want a list of packages used.