papaja (Preparing APA Journal Articles) is an R package that provides document formats to produce complete APA manuscripts from RMarkdown-files (PDF and Word documents) and helper functions that facilitate reporting statistics, tables, and plots.
Currently, papaja has some pretty heavy (indirect) dependecies, which we could strive to remove. Here are some ideas:
[x] gsl keeps giving users and our CI a hard time during installation. We rely on it indirectly through MBESS as a suggest. This should be solved shortyl, as MBESS has moved gsl to suggests.
[ ] stringr imports stringi, which takes a long time to install. The following packages we import use stringr:
knitr: The package uses stringr quite a bit, but there is an open PR to remove stringr over the medium term.
rmarkdown: There is only one call to stringr, which can probably be easily removed.
broom: There are several uses of stringr, but they should, in principle, be easy to remove.
[ ] broom: Has a heavy tidyverse dependency tree. We use it in some apa_print()-methods, but there we could switch to our alternative internal workflow (i.e. canonize() etc.) or use/support the output of a different package, such as parameters. Arguments for broom are the large number of supported models and it's widespread use, which makes it penatrable for independent contributors.
Currently,
papaja
has some pretty heavy (indirect) dependecies, which we could strive to remove. Here are some ideas:gsl
keeps giving users and our CI a hard time during installation. We rely on it indirectly throughMBESS
as a suggest. This should be solved shortyl, asMBESS
has movedgsl
to suggests.stringr
importsstringi
, which takes a long time to install. The following packages we import usestringr
:knitr
: The package usesstringr
quite a bit, but there is an open PR to removestringr
over the medium term.rmarkdown
: There is only one call tostringr
, which can probably be easily removed.broom
: There are several uses ofstringr
, but they should, in principle, be easy to remove.broom
: Has a heavy tidyverse dependency tree. We use it in someapa_print()
-methods, but there we could switch to our alternative internal workflow (i.e.canonize()
etc.) or use/support the output of a different package, such asparameters
. Arguments forbroom
are the large number of supported models and it's widespread use, which makes it penatrable for independent contributors.