-
Notifications
You must be signed in to change notification settings - Fork 233
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
Global option for markdown #515
Conversation
Also add the @nomd tag.
* Most fields can now be written using Markdown markup instead of the | ||
traditional Rd language. See the 'markdown' vignette for details | ||
(#364, #431), by @gaborcsardi | ||
(#364, #431, #499, #506, #507), by @gaborcsardi |
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.
Can you mention the global flag and @md
/@noMd
here too please?
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.
OK, so here. :) GH email notifications lose the context sometimes.
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.
OK, updated the NEWS.
I agree it's not the ideal approach but it works and doesn't need extensive changes to roxygen2. If you make that one change to NEWS.md, I'll merge |
Sure. You want another bullet point or in the same point? On 22 Sep 2016 14:15, "Hadley Wickham" notifications@github.com wrote:
|
Btw. I'll also |
Thanks! |
For #507
We read the options via the usual
load_options()
inroxygenize()
, and then push them down the call chain (almost) everywhere.parse_text()
also gets aglobal_options
argument.In each function where I added the
global_options
argument, I also added a default value (list()
), so that we don't break other packages.While this is done, and works, I don't think it is ideal. The best would be to attach the options to some
package
object, and make this reachable fromblock
objects. Roxygen does not really have the organization to implement this cleanly, AFAICT.Another option would be a global options store, but my problem with that is that it is hard to invalidate, and that these options really belong to the package and the blocks, not to roxygen itself.