Force index.php as fallback template when using block themes #382
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.
Currently the index.html template will take precedence over any views that have names that should be higher in the template hierarchy. This is because currently, we only stack the files on top of the blade templates when in reality they should be grouped by template names.
I've only noticed this as an issue when trying to use
home.blade.php
as a template for the posts lists but it gets overridden byindex.html
even though that should be a fallback. Movingindex.php
to the end of the list when it exists should ensure that it is only used as a fallback and doesn't take precedence over custom view templates.This is what the template hierarchy looks like right now
And this is what it should look like