-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Allowing config option to set which headers to extract #1111
Conversation
if (siteConfig.markdown && siteConfig.markdown.extractHeaders) { | ||
headersToExtract = siteConfig.markdown.extractHeaders | ||
} | ||
const headers = extractHeaders(content, headersToExtract, markdown) |
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 remember I have said that siteConfig
shouldn't be passed to markdown-loader
like a giant brick
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.
Should I just change this to pass in siteConfig.markdown
instead of all of siteConfig
?
@ulivz I think this is what you are talking about now |
316e022
to
1284944
Compare
We should take care about the search too with that to be sure all is working well |
Hello i'm closing this PR as it's now replace by this one #1730 Thank's for your work all ! |
Summary
This PR resolves #984
This PR replaces #1004
Currently the header parsing is hard coded to
['h2', 'h3']
. This code changes that to give the ability to configure this in thethemeOptions
config.What kind of change does this PR introduce? (check at least one)
If changing the UI of default theme, please provide the before/after screenshot:
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
fix #xxx[,#xxx]
, where "xxx" is the issue number)You have tested in the following browsers: (Providing a detailed version will be better.)
If adding a new feature, the PR's description includes:
To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.
Other information: