pkgnet
pkgnet copied to clipboard
R package for analyzing other R packages via graph representations of their dependencies
Currently, in `FunctionReporter$extract_network()` we have logic like this: ``` if (!is.null(private$pkg_path)){ private$calculate_test_coverage() } ``` This feels kind of awkward...instead of a user saying "add test coverage", we allow you to...
Given the conversation started by [{itdepends}](https://github.com/jimhester/itdepends), would it be possible to size nodes in the visualization by package weight? One option is to pick one metric from {itdepends} or make...
Currently in `R/AbstractGraphReporter.R`, we hardcode the color to use when plotting edges: ``` plotDTedges[, color := '#848484'] ``` To complete this issue, change `pkgnet` to allow people to configure this....
Now that datastorm-open/visNetwork#290 has been addressed, we do not need this protection in `AbstractGraphReporter`: ``` if (length(colorFieldValues) > 1) { g
Right now, the references section looks like this: I propose that we should: * hide the `Abstract*` completely * Put the two functions together in a section called "Functions" *...
If you render the visualization for the function network multiple times in a row, you will see a few different versions. To observe this, run: ``` library(pkgnet) t
It seems that the description of the color legend for the Dependency Network might be mixed up. For example, here is a screenshot after running `CreatePackageReport("devtools")`: The `devtools` node is...
`pkgnet::CreatePackageReport` misses function calls that happens within the arguments of a function. For instance `GetGruffiClusteringName` is a helper to guess `granuleRes` in `ParseGruffiGranuleScoreName`. [See more in gruffi](https://github.com/jn-goe/gruffi/) ```r ParseGruffiGranuleScoreName
Noticed this while trying to diagnose failing unit tests in #296. ```shell Rscript -e "remove.packages(c('pkgnet', 'baseballstats'))" R CMD INSTALL . R CMD INSTALL ./inst/baseballstats ``` Then, in R ```r library(pkgnet)...
Currently only required imports and depends dependencies are listed. The dependency tree does not include any 'linking to' type dependencies, which would be installed with the package, but do not...