fix(parser): Detect inline code with multiple inner backticks #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.
Currently, the parser fails to detect inline code that has multiple consecutive inner backticks (ex:
multiple ``inner`` backticks). This was an oversight on my part in PR #19 , as I failed to consider this edge case.The solution is fairly simple. Instead of preventing any occurrence of the starting backtick sequence inside the code span, we match until we find the proper terminating sequence, one that matches the opener exactly without preceding or subsequent backticks.
Old regex:
(?<!`)(`+)(?!`)((?:(?!\1).)+?)(\1)(?!`)New regex:
(?<!`)(`+)(?!`)(.*?)(?=(?<!`)\1(?!`))(\1)Before:
After:
Summary by cubic
Fix inline code parsing when the content includes consecutive inner backticks (e.g.,
code with ``inner`` backticks). The parser now finds the correct closing sequence that matches the opener, so code spans render correctly.multi-backtickcontent.