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
It is confusing that metalsmith & marked options must be specified at the same level of the options object.
markdown({ gfm: true, // -> marked opt keys: ['desc'] // -> metalsmith opt })
This has the risk of name collision and passes irrelevant options to marked. Better would be, as in metalsmith-in-place & layouts:
markdown({ keys: ['desc'], // -> metalsmith opt, engineOptions: { gfm: true, // -> marked opt } })
For 1.x both will continue to be supported, but add a deprecation warning. For 2.x root-level marked options will be removed
The text was updated successfully, but these errors were encountered:
5652c26
Successfully merging a pull request may close this issue.
It is confusing that metalsmith & marked options must be specified at the same level of the options object.
This has the risk of name collision and passes irrelevant options to marked.
Better would be, as in metalsmith-in-place & layouts:
For 1.x both will continue to be supported, but add a deprecation warning.
For 2.x root-level marked options will be removed
The text was updated successfully, but these errors were encountered: