Fix #1105: change order of markdown parsers to allow pipe characters in lists #1114
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
A better description would be: "to allow pipe characters in lists"; without this change, pipe tables in lists were possible, it was lines that could have been the first line of a pipe table, but were not, that caused problems. |
andreasabel
changed the title
|
Let's try this out, I suppose. However, we wouldn't see any feedback until the next deployment... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix #1105: change order of markdown parsers to allow pipes in lists
Workaround suggested at:
gfmExtensionsparser drops out of list when|is encountered jgm/commonmark-hs#95