Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
closes #11
Switching to a common-markdown compliant parser, since marked doesn't really follow any standard.
This does have the issue of not showing users what the markdown they wrote will look like when passed through the most popular parsers (so people like folks from notslang/atom-tidy-markdown#11 and #7 wouldn't find out their code is broken till they render it somewhere). However, I hope that more people will switch to common-markdown so this won't be a problem. And, I really don't want to force special formatting just to support the old / broken markdown standard.
Perhaps we should have an option to warn people when their markdown might break in old parsers... or have an option to format according to the old rules?