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
TLDR: until we provide a new syntax and deprecate the old one, I think it's fine to keep the docs as is.
I've added this issue for the Docusaurus v4 milestone, but it's not just documentation, it's also proposing and implementing the new syntax + a smooth migration plan.
When the mdxv1 compat option is turned on, are users expected to escape the heading id's or now.
The wording around "This syntax is now invalid" doesn't help would be users in understanding if thet are expected
to re-write the explicit ids with mdxv1compat turned on or not.
When the mdxv1 compat option is turned on, are users expected to escape the heading id's or now.
I recommend to not do anything and keep the heading as is until we provide a better replacement.
But there are cases where you might want need escape: if you use additional tools (like VSCode extensions, syntax highlighters or whatever else exists) that require a valid MDX document. Without escaping \{, your document is invalid, and it's possible that those tools report you errors (and they are right, because they don't know about our compatibility option).
That's the only reason I can think of to rewrite your headers with escaping right now. Unless you have a good reason to rewrite headings, you'd rather keep them as is.
Have you read the Contributing Guidelines on issues?
Description
The current docs didn't mention about the new syntax conventions (or options) for header ids as @slorber mentioned at #3321 (comment)
A bit more detail about that should ideally be added to the page https://docusaurus.io/docs/markdown-features/toc#heading-ids ?
Self-service
The text was updated successfully, but these errors were encountered: