improvement(core): include path in template errors #5692
Merged
Conversation
This file contains 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
thsig
force-pushed
the
include-path-in-template-errors
branch
from
4c13947
to
070e3a2
Compare
stefreak
reviewed
Feb 1, 2024
thsig
force-pushed
the
include-path-in-template-errors
branch
from
070e3a2
to
21ad031
Compare
stefreak
previously approved these changes
Feb 2, 2024
thsig
force-pushed
the
include-path-in-template-errors
branch
from
cc5ab04
to
df2a57f
Compare
thsig
force-pushed
the
include-path-in-template-errors
branch
from
df2a57f
to
d3c95e0
Compare
When available, include the path to the template string in the YAML doc in question. Also stop truncating the template expression in the message.
thsig
force-pushed
the
include-path-in-template-errors
branch
from
d3c95e0
to
00d204a
Compare
vvagaytsev
approved these changes
Feb 13, 2024
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.
What this PR does / why we need it:
When available, include the path to the template string in the YAML doc in question.
Also stop truncating the template expression in the message.