-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
RFC: Remove autolink support ✅ #1049
Comments
TL;DR (from here) on why I think they’re a bad idea to support:
|
Extra--while this is a bit far away for most folks except for John and me who have tried the new parsing out--we now have error messages that point to exactly where a typo/problem is, with a reason, and what was expected. That greatly improves developer experience. If we relax around things that might be a link, errors will start slipping through unnoticed. |
This means applying https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-plugin-mdx#migrating-from-v3-to-v4 As well as making mdx html compatible with jsx as mdx moved to jsx Additional references: - mdx-js/mdx#1049 - kentcdodds/mdx-bundler#122
mdxjs does not allow autolinks. See mdx-js/mdx#1049. We also added a linter check for the same. Preparatory commit for zulip#30451.
mdxjs does not allow autolinks. See mdx-js/mdx#1049. We also added a linter check for the same. Preparatory commit for #30451.
Autolinks are a feature in Markdown that allow you to wrap a url in angle brackets:
<https://mdxjs.com>
. Currently, in v1, we support them but with the parser changes in #1039 they've been dropped.This comes at a cost of breaking perfect interoperability with Markdown, but perhaps it makes sense because it makes
<
a clearer boundary for JSX syntax, which may be more clear to users. It might also be more confusing.This issue is for discussing the potential implications of removing autolink syntax.
The text was updated successfully, but these errors were encountered: