-
-
Notifications
You must be signed in to change notification settings - Fork 267
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
feat(content): update marked to latest version and fix custom renderer compatibility #1658
base: beta
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for analog-ng-app ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for analog-blog ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for analog-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for analog-app ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
e02ac16
to
09f9ee4
Compare
09f9ee4
to
253e5ad
Compare
Thanks @kudoas If we automatically update the package.json with the updated versions, this won't be breaking right? |
Thanks for pointing that out — you're right, if package.json is updated automatically, it shouldn't be breaking. |
PR Checklist
Closes #1420
Closes #1535
What is the new behavior?
Custom renderer now properly handles tokenized inputs introduced in marked v13+, ensuring consistent markdown rendering.
Does this PR introduce a breaking change?
Other information
[optional] What gif best describes this PR or how it makes you feel?