Identify where was the broken reference was declared#103
Merged
Conversation
added 10 commits
April 14, 2017 16:50
…-the-broken-reference-declared
Contributor
Author
|
Have been testing this internally at GitHub for several days and it's working as intended. |
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
1 participant
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.
This pull request enhances the reference validation feature error message. If a broken reference is found, the error message will now indicate the source file and line.
It appears that Puppet 3.x and 4.x compute the line numbers differently. One displays the first line of the block, and the other displays the last line of the block. However the information is still useful.