You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes a function can be passing some parameters directly to foo(), others directly to bar(). Naturally to avoid repetition, we want to @inheritParams from both of them (assuming there's no conflict, etc):
Unfortunately, my first instinct was to try @inheritParams foo bar which seems like a natural choice given how many other @ tags in {roxygen2} work similarly:
If there's a reason not to allow multiple space-separated topics here, then we should just document this. I looked at vignettes("reuse") and didn't see this case discussed.
If we should just allow space-separated entries, probably the case should still be discussed in vignettes("reuse").
I can try my hand at a PR; filing an issue first for the design guidance before proceeding.
The text was updated successfully, but these errors were encountered:
Sometimes a function can be passing some parameters directly to
foo()
, others directly tobar()
. Naturally to avoid repetition, we want to@inheritParams
from both of them (assuming there's no conflict, etc):Unfortunately, my first instinct was to try
@inheritParams foo bar
which seems like a natural choice given how many other@
tags in {roxygen2} work similarly:If there's a reason not to allow multiple space-separated topics here, then we should just document this. I looked at
vignettes("reuse")
and didn't see this case discussed.If we should just allow space-separated entries, probably the case should still be discussed in
vignettes("reuse")
.I can try my hand at a PR; filing an issue first for the design guidance before proceeding.
The text was updated successfully, but these errors were encountered: