You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've tried to update marked up to v0.3.19 and compare results for the same sources set from the master branch. There are many diffs in them. I cannot enumerate and analyze all of them, but there are some I can mention by the first glance.
Node.js uses doc linking with @include directives combining all the docs in all.html file. In this file, all the Node.js doc file names are deleted from the relative link URLs, so that cross-document links become intra-document links. In v0.3.19 this deleting is broken:
@vsemozhetbyt: Gonna go ahead and close this per #1106 and the zero major. We're definitely trying to fix more than we break in the long run. Thank you for the contributions you made along with point this one out. We're getting closer to having a better idea of exactly how of the mark marked is compared to the CommonMark spec (see #1160); so, hopefully a truly stable release is somewhere in the near future (compared to there just not be a release for a while).
Node.js uses marked
v0.3.6
in its doc tools for building docs md sources.I've tried to update marked up to
v0.3.19
and compare results for the same sources set from the master branch. There are many diffs in them. I cannot enumerate and analyze all of them, but there are some I can mention by the first glance.Parsing code inside links with link references:
Source:
HTML:
Node.js uses doc linking with
@include
directives combining all the docs inall.html
file. In this file, all the Node.js doc file names are deleted from the relative link URLs, so that cross-document links become intra-document links. In v0.3.19 this deleting is broken:Source:
HTML:
Here is a zip with two folders with results if somebody wants to dig into all the diffs.
Sorry if this is not a relevant information concerning zero prerelease.
The text was updated successfully, but these errors were encountered: