Laura Bąkała
Laura Bąkała
Sometimes packages have version names that don't fit into `is_package_version()` requirements. For example, `xtable`, which consistently names its versions in `1.X-X` pattern. These names are returned by `cran_package_history()` and I'd...
There should be a way to generate `deepdep` object for given package without depth limit. It would be intuitive to achieve this by using `depth = Inf`, but our current...
When you call: ``` deepdep::deepdep("versionsort") ``` and ``` deepdep::deepdep("stringi") ``` the returned data frames have different columns:  The latter are correct, probably the effect of deleting base R dependencies...
Package weight could be a parameter of `deepdep()` function or a function applied to a `deepdep` object. I don't like parameter bloat, so I'd opt for the latter solution. This...
Best implemented as an S3 method. The call would look like: ```r dd
It would create a deepdep plot and insert it in a separate section at the bottom of `README.md` (or maybe a code chunk in `README.Rmd` instead?).
**Description of a problem related to your idea** I'd like to compare differences between dependencies used in different versions of a package; e.g. differences between deepdep v0.2.0 and deepdep v0.4.1....
It would probably have to be done by overwriting layer colors; perhaps a separate visualization? It could be helpful when tracking if no license clash occurs.
When passing a character vector of packages to `plot_download()`, the title is incorrect; this is the result of the following call: ```r plot_downloads(c("versionsort", "deepdep")) ```  Clearly, `versionsort` and `deepdep`...
It would be easier to read the numbers if there were some separators each three digits. 