Fix link definition parsing being too greedy #81
Merged
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.
Currently, the following snippet:
will be parsed as
leading to somewhat surprising results. This happens not only when that construct is the start of a paragraph, but also when it is the start of a list item:
First link does not render, the second one will. This behavior is rooted in an somewhat too greedy approach to identifying the closing
]:when a link definition is possible.This commit fixes that by asserting that
]:is found at the first occurance of]when looking for a LinkDefinition.