Markdown parsing has changed dramatically #2158
-
Hi!
Is there any way to bring old parsing back? I have tons of content and it's impossible to fix it for me.... Here's full package.json if it helps: https://github.com/dimaip/calendar/blob/master/package.json |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
That’s how CommonMark, which is used in lots of places, including here on GitHub, works. |
Beta Was this translation helpful? Give feedback.
-
Hey @dimaip!
To be clear, markdown parsing stayed largely the same.
These are some of the edge cases. **aaaa ** aaaa**)**aaaa
No, bugs will not be re-added to MDX.
I'd recommend transforming content with code to make it valid CommonMark/GFM in an automated way. |
Beta Was this translation helpful? Give feedback.
Hey @dimaip!
Sorry to hear you ran into a spot of trouble, happy to talk through options.
To be clear, markdown parsing stayed largely the same.
The only differences are some bugfixes to correctly align edge cases to the CommonMark and GFM standards.
These are some of the edge cases.
Previewing that code in GitHub itself you can see it is not bolded either.
**aaaa **
aaaa**)**aaaa
No, bugs will not be re-added to MDX.
And especially not bugs from a pre-alpha release.