Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[commonmark] make code fences compliant (+ fix 1058) #1387

Merged
merged 5 commits into from Dec 10, 2018
Merged

[commonmark] make code fences compliant (+ fix 1058) #1387

merged 5 commits into from Dec 10, 2018

Commits on Dec 8, 2018

  1. require closing fence to be on a new line (fix markedjs#1058), while … 

    …still allowing empty code blocks
    @Feder1co5oave
    Feder1co5oave committed Dec 8, 2018
    Copy the full SHA
    67a5941 View commit details
    Browse the repository at this point in the history

  2. allow the closing fence to be longer that the opening one (pass cm ex… 

    …ample 93)
    @Feder1co5oave
    Feder1co5oave committed Dec 8, 2018
    Copy the full SHA
    d0aa0b1 View commit details
    Browse the repository at this point in the history

  3. handle fenced code blocks ended by end of file (or parent container) … 

    …and info string compliant to commonmark
    @Feder1co5oave
    Feder1co5oave committed Dec 8, 2018
    Copy the full SHA
    2f19392 View commit details
    Browse the repository at this point in the history

  4. fences must be indent up to 3 spaces (pass cm example 106)

    @Feder1co5oave
    Feder1co5oave committed Dec 8, 2018
    Copy the full SHA
    30a73a3 View commit details
    Browse the repository at this point in the history

  5. use only the first word of the inforstring as the languauge in code b… 

    …locks (pass cm example 112)
    @Feder1co5oave
    Feder1co5oave committed Dec 8, 2018
    Copy the full SHA
    ca52d38 View commit details
    Browse the repository at this point in the history