#4134. Add/update tests regarding whitespaces and interrupting lines #4135
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.
Some comments to this PR.
test_removesSpaceAfterTripleSlashesis failing. But the specification clearly states thatSo, I believe it is a bug in the current implementation. It should be fixed to follow the spec.
test_whitespacesInCodeSpanalso fails. The spec says that whitespaces inside fenced code blocks should be preserved. But in this test we have a code span (`). Spec says that fenced code blocks are the only exception in all other cases all leading whitespaces should be removed. Therefore it is an implementation issue again.```)...". Github flavored markdown also supports~~~as begin/end of code blocks. Probably it makes sense to mention it to the spec. Say "Exception: inside fenced code blocks (``` or ~~~)...".cc @srawlins because the change affects his comment.