We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We should create a convenient configuration mechanism for configuring the pipeline.
As @joshua-light mentioned in #46 (comment):
What do you think about extracting a new MdRendererOptions class for tweaking such things? For example, we could call the UseMdRenderer method on the pipeline with few ways: (the old one) pipeline .UseMdRenderer("..."); (the more customizable one) pipeline .UseMdRenderer(options => options .CleanupOutputDir() .UseGitHubMarkdown())
What do you think about extracting a new MdRendererOptions class for tweaking such things?
MdRendererOptions
For example, we could call the UseMdRenderer method on the pipeline with few ways:
UseMdRenderer
(the old one)
pipeline .UseMdRenderer("...");
(the more customizable one)
pipeline .UseMdRenderer(options => options .CleanupOutputDir() .UseGitHubMarkdown())
The text was updated successfully, but these errors were encountered:
No branches or pull requests
We should create a convenient configuration mechanism for configuring the pipeline.
As @joshua-light mentioned in #46 (comment):
The text was updated successfully, but these errors were encountered: