-
Notifications
You must be signed in to change notification settings - Fork 1.1k
chore: use rehype plugin for heading id generation #7701
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
Conversation
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.
We're not using this anywhere else.
@@ -50,33 +53,4 @@ describe('MDXHeading', () => { | |||
expect(heading).toHaveTextContent(props.children); | |||
expect(link).not.toBeInTheDocument(); | |||
}); | |||
|
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.
We're not handling the ID generation anymore so I removed these tests.
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.
This page was using a work around to generate H3's with a unique ID using another component. But now we can use normal markdown headings. Also changes some headings to h4. Preview
Description of changes:
This PR adds a rehype-slug plugin that generates a unique ID for headings. Duplicate headings will have an incremented number attached to them; i.e.
#options
and#options-1
. This fixes an issue where some H3 table of content links with the same name would link to the same heading because we were generating the same id for that heading.Pages to test:
<code>
element as childrenRelated GitHub issue #, if available:
Fixes: #6748
Instructions
If this PR should not be merged upon approval for any reason, please submit as a DRAFT
Which product(s) are affected by this PR (if applicable)?
Which platform(s) are affected by this PR (if applicable)?
Please add the product(s)/platform(s) affected to the PR title
Checks
Does this PR conform to the styleguide?
Does this PR include filetypes other than markdown or images? Please add or update unit tests accordingly.
Are any files being deleted with this PR? If so, have the needed redirects been created?
Are all links in MDX files using the MDX link syntax rather than HTML link syntax?
ref: MDX:
[link](https://docs.amplify.aws/)
HTML:
<a href="https://docs.amplify.aws/">link</a>
When this PR is ready to merge, please check the box below
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.