[code-infra] Move ComponentLinkHeader to @mui/docs #42061
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Janpot
changed the title
michaldudak
approved these changes
Apr 30, 2024
There was a problem hiding this comment.
Nice, Base UI seems to work with this: mui/base-ui#378.
The only remaining component we need to have locally is ComponentPageTabs.
| @@ -12,7 +12,15 @@ export function createRender(context: { | |||
| ignoreLanguagePages: (path: string) => boolean; | |||
| }): (markdown: string) => string; | |||
|
|
|||
| export function getHeaders(markdown: string): Record<string, string | string[]>; | |||
| export interface MarkdownHeaders { | |||
There was a problem hiding this comment.
These headers also include components and hooks.
There was a problem hiding this comment.
Added those and removed some of the typescript casts
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@mui/docs/...@mui/docsComponentLinkHeader. We could think about supporting named exports with something like: