fix parser issue with input ending with non-space characters #28
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.
Discovered that the input string that ends with non-whitespace characters caused an incorrect parsing. For example, the following input (fenced code block with no newlines at the end)
is parsed as a fenced code block followed by another paragraph with text value of "`".
I don't know if the spec requires all input string to end with 1+ newline characters or not, but, appending a whitespace character at the end fixed most of my own use cases. Feel free to close/ignore if you have a better fix 😄 .
Thanks!