You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As originally reported in #9428, the Meta block doesn't take an id prop, making it impossible to assign a permalink to MDX documentation pages. This hasn't changed in the releases since the original issue, and it still seems like a bug to me.
Quoting:
Currently in V 5.3 the docs-block has a title property from which the docs-page URL is generated, e.g. the title "DesignSystem / Component / MyButton" creates a route like http://...path/=/docs/designsystem-components-mybutton--page. If we change the title of the docs page, then the link is broken. It would be better if the Meta-Tag could receive an id which enables you to permalink to the page.
Typical use case: Initial creation of pages from entities of your design process where a draft-name and a guid is given e.g. MyButton with guid 781e6e22-e3d2-4ca7-835b-a8b65095bfc0. In later implementation steps, the name may change to TheButton whereas the guid remains the same. Links from design artifacts into storybook should stay the same as they reference the same entity (permalink).
This doesn't really apply; if you're so inclined, open up the repro, check the id="home" on the Meta block, and witness how the link to the story doesn't change.
Describe the bug
As originally reported in #9428, the
Meta
block doesn't take anid
prop, making it impossible to assign a permalink to MDX documentation pages. This hasn't changed in the releases since the original issue, and it still seems like a bug to me.Quoting:
Reproduction link
https://stackblitz.com/edit/github-zgrofuhl?file=src%2Fstories%2FConfigure.mdx
Reproduction steps
This doesn't really apply; if you're so inclined, open up the repro, check the
id="home"
on the Meta block, and witness how the link to the story doesn't change.System
Additional context
No response
The text was updated successfully, but these errors were encountered: