🐛 FIX: Source line reporting for nested parsing#490
Merged
chrisjsewell merged 1 commit intomasterfrom Jan 4, 2022
Merged
Conversation
Previously, nested parsing of content within directives would not correctly propagate the starting line number of the content.
Codecov Report
@@ Coverage Diff @@
## master #490 +/- ##
==========================================
+ Coverage 89.86% 89.89% +0.02%
==========================================
Files 16 16
Lines 2062 2068 +6
==========================================
+ Hits 1853 1859 +6
Misses 209 209
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Merged
This file contains hidden or 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
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.
Previously, nested parsing of content within directives
would not correctly propagate the starting line number
of the content.
For example:
Would incorrectly report the error on line 1:
but now correctly reports on line 7: