Carl A. B. Pearson

@bwiernik i've proposed a revision that addresses this, by changing where `...` points to (namely, `label_numeric`, which includes the `style_(positive|negative)` documentation). is that a sufficient change?

Hmm, agree. Wait one. On Tue, Aug 30, 2022 at 11:52 AM Teun van den Brand < ***@***.***> wrote: > I'm not a maintainer of this package, but it seems...

Okay, so yes, but: https://github.com/r-lib/roxygen2/issues/633 - inheriting dots does not properly document that even more arguments may be passed on from wrapped function. To address *this* issue, I think `@inheritDotParams`...

I'm one of the full time series folks. I'm using this for global projection models on a by-country basis. We estimate an intervention time, a pre-intervention R (which is way...

n.b., switching to a `ringbp::parameters()` approach (per #65) might also deal with this handily.

Hmm - so is the idea here to have ```r res

I'd guess the most-likely-to-make-this-happen next step is to provide (here?) focused snippets showing where `pepbp` had to diverge from `ringbp` to do what you needed. I imagine that development went...

> > The alternative option would be to provide some documentation on "how to spin off your own model by using a fork", bringing in any lessons learned in previous...

> A version of this problem came up in a recent discussion with simulist ([epiverse-trace/simulist#58](https://github.com/epiverse-trace/simulist/issues/58)), when we wanted to incorporate simulation of contacts as well as secondary cases into [epichains](https://github.com/epiverse-trace/epichains/)....

for consistency with general R language conventions, should probably be: ```r res