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.

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 initial, final newlines in fenced code #423

Merged
merged 1 commit into from
Jul 15, 2019
Merged

Conversation

wooorm
Copy link
Member

@wooorm wooorm commented Jul 15, 2019

Closes GH-351.

@wooorm wooorm requested a review from a team July 15, 2019 09:18
@wooorm wooorm merged commit f89fd77 into master Jul 15, 2019
@wooorm wooorm deleted the fenced-code-newlines branch July 15, 2019 17:08
btmills added a commit to eslint/markdown that referenced this pull request Feb 27, 2021
`remark-parse@7.0.0` includes
remarkjs/remark#423, which fixes handling of
leading and trailing newlines in fenced code blocks.

Tagging this as `Update` so it'll be semver-minor. Are we comfortable
with a parser major version bump in a semver-minor release?
btmills added a commit to eslint/markdown that referenced this pull request Apr 25, 2021
`remark-parse@7.0.0` includes
remarkjs/remark#423, which fixes handling of
leading and trailing newlines in fenced code blocks.

Tagging this as `Update` so it'll be semver-minor. Are we comfortable
with a parser major version bump in a semver-minor release?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

[CommonMark] Leading/trailing newlines are stripped in the value of fenced codeblock
3 participants