Catch exception in detectLineNumber for not existing blade files. #299
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 stumbled over this while testing mocked blade views. In that case I just want to test the compiled view without having an existing template file. Whenever there is an exception in the view,
detectLineNumber
inFacade\Ignition\Views\Compilers\BladeSourceMapCompiler
fails, since it cannot open the view path. However I would like to see the exceptions in my views anyway. I suggest to return line number1
in that case.This is the exception I get when I render mocked blade templates:
With catching the
ErrorException
: