-
Notifications
You must be signed in to change notification settings - Fork 12
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
Option to not generate an HTML/Markdown output #8
Comments
Just to make sure we're on the same page: the I do see your point that it shouldn't generate the HTML by default. I'd be happy to accept a PR that only generates the HTML if the |
Yeah, you’re right of course:
Well I’ll see if I can get a PR together but I’m unfortunately a bit busy at the moment. :-/ |
Got it. I'm away without a computer until the 19th and have a few pressing contracts to work on when back so I also won't do much other than accept PRs :) |
In my opinion, ezknitr does a bit too much:
At the moment, ezknitr always generates HTML output via
markdown::markdownToHTML
. I’d argue that this shouldn’t happen by default (it’s fundamentally a separate concern from knitting a file). However, such a change would break backwards compatibility.At the very least it should be optional though, because the user (= yours truly) may want to have more control over how the HTML is generated (or, indeed, not generate any HTML output at all). The only recourse at the moment is to delete the generated HTML and re-generate it differently, a wasteful process.
The same, to a lesser extent, is true for the generation of an .md file (when the user calls
ezspin
).The text was updated successfully, but these errors were encountered: