Avoiding double-wrapping of Twig RuntimeError #1132
Merged
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.
I had noticed that, when making a typo in my Twig file, the true error was hidden inside a nested exception.
Before (left top of page, right, further down the page)
After
So, you see the exact error now. You lose that the error happened when rendering the
InvoiceCreator
component, but I think that's not important. And you can find that actually if you look up the stacktrace a bit.Btw, the reason we want to throw a
RuntimeError
from Twig is if, when rendering, if you have an error in your PHP code (not template), it makes it look nicer. Without wrapping your PHP error in aRuntimeError
, you get:After, it is:
So the
RuntimeError
is 👍 ... but we don't need to create a 2nd one if we already have one.Cheers!