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 by index.html even though that should be a fallback. Moving index.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
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.phpas a template for the posts lists but it gets overridden byindex.htmleven though that should be a fallback. Movingindex.phpto 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