-
-
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
chore(package): update marked 0.3.9 to 0.6.1 #87
Conversation
* marked 0.4.0 is Compliant with GFM task list * markedjs/marked#1250
I would like to test changes in rendering for both cases: lists and checkbox, before validating. It would deserve a minor or major version bump. And we should check the rendering of our default theme |
OK. I will try it later.
OK. It's better. But, how to do? Manually & visually? I have no idea... |
I'll try to do it manually this week end. I'll setup a test site |
OK. May I help you? |
Here is the result before: And after: I'd say it improved! checkboxes unchecked are working. Also, I tested with commenting the autolink feature, and it still works The heading code seems to still be necessary, same for Description Lists. You should adapt code and drop tests unnecessary So considering all this, we definitely should bump the major version (changes in rendering) It will also allow us to close a bunch of checkbox related PR/Issues |
* GFM list is implemented in marked 0.4.0
I bump to marked 0.6.1 & drop self implemented todo list. |
I just noticed this branch fixes the #86. However, it breaks the tables! @yoshinorin Should we add unit tests for this tables so they don't break on future updates?
Rendering with Marked 0.6Before this table used look like this: Rendering with Marked 0.3 |
@amejiarosario @tomap |
@yoshinorin the breaking change is that marked is less forgiving. My table was missing a |
@yoshinorin the coverage decreased hexo-renderer-marked/test/index.js Line 89 in f81890c
and cover the case of sanatize that is not covered |
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.
Increasing the coverage would be nice, but appart from that, I validate
@tomap Thank you review :) Coverage decrease is caused by delete source code (Not include test code). This PR delete self-implemented TODO-list. My understnding, the coveralls calculate coverage based on how many lines of the total code lines were tested. So, If source code delete, coverage will be decrease. |
Is this means... Will you validate this PR? |
@tomap Thanks :) |
I think we should merge |
Merged Thanks :) |
Details
Update marked from 0.3.9 to 0.6.0 & fixed testcode for breaking change in marked v0.4.0