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
Add option to control wrapping #142
Conversation
Add ability to change default roclets
The log of the last build, line 726, shows:
Can this become a problem? |
That's just a note, so I think it's ok. R-exts says "There is no restriction on the use of other fields not mentioned here (but using other capitalizations of these field names would cause confusion)." |
@@ -22,6 +22,7 @@ Imports: | |||
Suggests: | |||
testthat | |||
LinkingTo: Rcpp | |||
Roxygen: list(wrap = FALSE) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this the permanent solution, or will there be a nicer syntax like
Roxygen:
wrap
other_option=value
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd prefer to stick to R code since it's straightforward to parse.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was just wondering if the name Roxygen@R
would thus be more appropriate - since somehow consistent with the Authors@R
field... However, if there is no plain text equivalent specification, sticking to a pure Roxygen
definitely seems nicer.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I thought about that too, but on the balance, I think I prefer just Roxygen
This also provides a straightforward mechanism to add other options to roxygen if need be (options should be reserved strictly for controlling backward compatibility, otherwise it is increases the testing load).
Fixes #132.