storage/framework/views folder is being used for specific views now? How come my laravel 5.3 spark application views for login, register and a few other ones are pulling from the folder
storage/framework/views
and not my standard
resources/views/vendor/spark/auth folder?
Looks like doing php artisan view:clear updates all these views then however what is the purpose?
Do i really have to use this command now everytime I want to update my views?
All views are parsed by the framework and placed in the storage directory. Think of these as the 'compiled' PHP files of your Blade code.
Blade code cannot execute on its own.
Also it's the views cache. So it doesn't have to parse every call
This could be left out in the future.
Considering that php have own file caching AND
debbuging rendered file is hideous.
Plus u need render which makes the code slower.
@include
@foreach
etc.
short tags will not give anything compared to php
include('');
foreach(){}
The idea its self is also from late 90s.
Making the framework could think of it, to make programming easier and faster
not for "this is fancy" lets to so.
I hope your next direction is "easier and faster".
Regards.
Please sign in or create an account to participate in this conversation.