Adds event "twigLoaderPreInit.customize" #32
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.
This allows plugins to manipulate the loaders list before the Twig Environment is initialized. There already is an event after initialization that allows one to change many things with the Twig Environment, however the problem I came across was when one tried to add more loaders. Turns out that no loader can go after
Twig_Loader_String
as that loader will interpret anything as a template and try to render it, so no loader can come after it. That is used by core for the rendering of the header and footer. It also is responsible for the mis-typed twig paths to simply output something like this:I'd like to get that fixed as that's a silent error, but that's another issue for another day.