Rémi Thériault
Rémi Thériault
Also should `cite_easystats()` move to the `easystats` meta-package? I think it would make more sense than in report??
Apologies I completely missed this somehow. Will get onto it soon
I thought why not but we can remove if that feels confusing given the paper. Edit: My reasoning was as is the paper doesn't have any link to the `easystats`...
I think it is a little bit strange that we don't demonstrate a single function from the paper's package (instead of wider ecosystem), however, I don't know what would be...
> How about a tree-like diagram where `insight` is the root at the bottom, then `datawizard` is the trunk and then all the other packages are the leaves? I agree...
> do we have a new bug in _report_ that duplicates some lines? shit, sorry, let me investigate
> I know it's ugly AF, but, e.g. Nice, I like it. But I'd add easystats on the right maybe with arrows from all relevant layers (core, analysis, and user...
> Like so? Na, because easystats is not just the ecosystem, it's also an actual package that would deserve its own box! But making it clear which functions it leverages
Package coveraged increased to 81%, which is good, almost a 10% improvement. However, it seems like the following are still at 0% ```r R/report.brmsfit.R: 0.00% R/report.compare.loo.R: 0.00% R/report.glmmTMB.R: 0.00% R/report.MixMod.R:...
Package coveraged increased from 81% to 86%, a good improvement, with critical coverage gains in the previously affected functions (that had 0% coverage). However, there is still room to increase...