-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
[MDX] Add getHeadings
+ generate anchor links
#4095
Conversation
🦋 Changeset detectedLatest commit: d061b9e The changes in this PR will be included in the next version bump. This PR includes changesets to release 5 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
Looks good! Just one note related to a bit of extra test coverage 👍
let fixture; | ||
|
||
before(async () => { | ||
fixture = await loadFixture({ |
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.
Would you mind adding a suite to test removing the default plugin as well?
Would be great to know CI will catch if we accidentally break that code path later assuming the headings are always added
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.
Added rehype-plugins
fixture to mirror our remark-plugins
fixture!
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.
Thank you for running the anchor leg on the MDX relay @bholmesdev! Left a few README comments but this is heading in the right direction!
|
||
export default { | ||
integrations: [mdx({ | ||
rehypePlugins: { extends: [rehypeMinifyHtml] }, |
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.
Does this syntax also work in markdown.rehypePlugins
? I currently do something like this to preserve defaults:
import { DEFAULT_REHYPE_PLUGINS } from '@astrojs/markdown-remark';
export default {
markdown: {
rehypePlugins: [...DEFAULT_REHYPE_PLUGINS, myExtraPlugin()],
},
}
I like the extends
format, but might be smart to make sure these APIs are consistent?
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.
Strong agree on this!
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.
It doesn't work yet, no! I introduced extends
to workshop a new API. I'll make an issue to update Markdown now that we like it 😁
|
||
export default { | ||
integrations: [mdx({ | ||
rehypePlugins: { extends: [rehypeMinifyHtml] }, |
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.
Strong agree on this!
Co-authored-by: Chris Swithinbank <[email protected]>
Co-authored-by: Chris Swithinbank <[email protected]>
…to feat/mdx-get-headings
Changes
id
s on all MDX headings via a rehype pluginrehypePlugins
config optiongetHeadings
to MDX file exportsTesting
Add test for ID generation and
getHeadings
with and without JSX expressionsDocs
Add generated exports to MDX README