-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reporting templates and the report
package
#495
Comments
Indeed. So we used these initially for our reporting and as far as I am aware no one else has ever used them.... (that being said its hard to know). I think one option would be just to remove these templates? The |
Yes, like {EpiNow2Extras} 🔥 |
Yes exactly. @sbfnk was interested for a while in making a little package ecosystem and moving things like In the first instance perhaps we should just drop these templates as we don't really want to support them or at least remove references to them in the README (or in the soon to be getting started guide). |
What was the agreement here? Are we removing the reporting templates and all references to them? |
EpiNow2 has reporting templates and are briefly mentioned in the README but there's no guidance on how exactly to use them or whether we even encourage users to use them. I recently came across the report package that provides nice methods for reporting fitted models from the common modelling functions in R like
lm
, etc, and other well known model objects from the Bayesian world likebrms
andrstanarm
.I wonder if we could/should upgrade the templates here to methods to work with the S3 classes returned by the various functions, especially after the work in #451, or whether it would be better to contribute
reports
methods to the {reports} package and link there.Thoughts?
The text was updated successfully, but these errors were encountered: