-
Notifications
You must be signed in to change notification settings - Fork 94
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 front matter rendering #3460
Conversation
If the editor was loaded before the callback did not write the front matter content to the correct variable which resulted in dropping the front matter. This is fixed by not using the callback but a renderer function. Signed-off-by: Ferdinand Thiessen <[email protected]>
/compile |
Test summaryRun details
View run in Cypress Dashboard ➡️ Flakiness
This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard |
1. Test if the correct front matter content is displayed 2. Test if the front matter survives closing and reopening the editor Skip common mark tests which we correctly interpret as front matter Signed-off-by: Ferdinand Thiessen <[email protected]>
Signed-off-by: nextcloud-command <[email protected]>
e21d523
to
984edbf
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code changes look good.
Tests included and seem to cover the issue in question - so i did not test myself.
[Stable25] Backport of #3460 - Fix front matter rendering
📝 Summary
This fixes an issue where front matters are not correctly rendered by markdown-it leading to an invalid tiptap state which is then the reason why front matters are sometimes dropped.
I also added a test for this.
🏁 Checklist
npm run lint
/npm run stylelint
/composer run cs:check
)