-
-
Notifications
You must be signed in to change notification settings - Fork 623
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
fix(markdown): detect inline component followed non whitespace characters #1227
Conversation
β Deploy Preview for nuxt-content ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
@farnabaz thanks for getting started right away. I think there should be more characters allowed than just dot and comma. Question marks, exclamation marks, colons, semi colons, etc. I wonder (especially if you used square brackets and curly brackets before), if just any character that cannot be used in a component name should be allowed. |
@leipert You are right, only ASCII chars, |
.
and ,
β¦ters (#1227) * fix(markdown): detect inline component followed by `.` and `,` * test: add test * chore: code style * fix: detect inline component regardless of ending character * test: update tests * docs(mdc): add example for inline ending chars * test: fix Co-authored-by: YaΓ«l Guilloux <yael.guilloux@gmail.com>
π Linked issue
resolves #1217
β Type of change
π Description
π Checklist