-
Notifications
You must be signed in to change notification settings - Fork 235
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
Documenting R6 objects #835
Comments
Duplicate of #388. See existing packages for what you can do right now. E.g. processx or webdriver, etc. |
Hi @gaborcsardi , I mentioned #388 in my question too, but it doesn't explain the behavior I'm seeing (or whatever my misunderstanding of the |
I'm going to close this ticket and open a new ticket that simplifies the issue and takes R6 out of the picture - to me this is just a vanilla |
I asked this question on Stack Overflow about how to document R6 objects, but no answers yet after a week: https://stackoverflow.com/questions/53750453/roxygen-r6-methods . Wondering if someone here might have a suggestion.
(I know R6 documentation is an oft-desired topic, as shown in the uncompleted issues #388, #306, etc. - basically I'm trying to "punt" and not need Roxygen to know anything about R6; I'm just trying to use some existing Roxygen features like
@inheritParams
etc. and haveR CMD check
not yell at me.)Question repeated here:
I'm trying to generate some reasonable documentation for R6 classes. Here's an example:
.public()
is a helper function I've written for defining R6 methods.There are several things not working here:
@inheritParams
directive is not working, thename
anddeps
andcreate
argument formyOtherMethod()
are not being inherited. This generatesR CMD check
warnings likeUndocumented arguments in documentation object 'myOtherMethod' ‘name’ ‘deps’ ‘create’
@usage
directive manually, because Roxygen can't figure out (quite reasonably) how to parse my method definitions. Is there a better way to do this?R CMD check
, I get warnings aboutFunctions or methods with usage in documentation object 'myMethod' but not in code: myMethod
Is there a more fruitful direction for me to go? Should I try documenting a
NULL
object instead of my.public
calls? What would that look like?The text was updated successfully, but these errors were encountered: