-
-
Notifications
You must be signed in to change notification settings - Fork 9.7k
Improved the error message when a template is not found #17434
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 1 commit
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
d3fe07b
[TwigBundle] fixed Include file locations in "Template could not be f…
rvanginneken e9d951a
[CodingStandards] Conformed to coding standards
rvanginneken 968476b
Improved the error message when a template is not found
javiereguiluz 35f082f
Fixed a syntax issue
javiereguiluz 88b913b
Fixed the problem in an easier way
javiereguiluz 19bfa2e
Added a test
javiereguiluz 0134d76
Simplified everything
javiereguiluz File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Fixed the problem in an easier way
- Loading branch information
commit 88b913b0c465dd805d679a0642aba4fd17a20241
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At this point, why not just rethrow the previous exception if it is a
Twig_Error_loader
exception?throw $previous
would do the same, no?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The problem is that there are two
$previous
. The first one is "the good one" ... but we always override it. If I usethrow $previous
the error message is worse:There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure I understand. Instead of storing
$errorMessage = $e->getMessage();
, why not store the exception itself and throw it here?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are right. I tried to maintain the existing code ... but it doesn't make sense. Updated. Thanks!