Utilize afterResolving for Laravel 6.10 and up #267
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
bakerkretzmar
approved these changes
May 2, 2020
|
Could we use $this->callAfterResolving('blade.compiler', function (BladeCompiler $compiler) {
$compiler->directive(/* ... */);
}); |
|
@bakerkretzmar I don't think so, because this would break compatibility with lower versions of Laravel that do not have that feature. |
|
Ahh right of course. Thanks! |
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.
A fix was implemented in Laravel 6.10 making the framework no longer resolve the blade compiler on start up (laravel/framework#31009).
The following change utilizes this improvement by not calling the compiler directly if it's not yet been resolved.