mirror of
https://github.com/invoiceninja/invoiceninja.git
synced 2024-11-09 12:42:36 +01:00
ba75a44eb8
* Adopt Laravel coding style The Laravel framework adopts the PSR-2 coding style with some additions. Laravel apps *should* adopt this coding style as well. However, Shift allows you to customize the adopted coding style by adding your own [PHP CS Fixer][1] `.php_cs` config to your project. You may use [Shift's .php_cs][2] file as a base. [1]: https://github.com/FriendsOfPHP/PHP-CS-Fixer [2]: https://gist.github.com/laravel-shift/cab527923ed2a109dda047b97d53c200 * Shift bindings PHP 5.5.9+ adds the new static `class` property which provides the fully qualified class name. This is preferred over using class name strings as these references are checked by the parser. * Shift core files * Shift to Throwable * Add laravel/ui dependency * Unindent vendor mail templates * Shift config files * Default config files In an effort to make upgrading the constantly changing config files easier, Shift defaulted them so you can review the commit diff for changes. Moving forward, you should use ENV variables or create a separate config file to allow the core config files to remain automatically upgradeable. * Shift Laravel dependencies * Shift cleanup * Upgrade to Laravel 7 Co-authored-by: Laravel Shift <shift@laravelshift.com>
37 lines
1.0 KiB
PHP
37 lines
1.0 KiB
PHP
<?php
|
|
|
|
return [
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| View Storage Paths
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| Most templating systems load templates from disk. Here you may specify
|
|
| an array of paths that should be checked for your views. Of course
|
|
| the usual Laravel view path has already been registered for you.
|
|
|
|
|
*/
|
|
|
|
'paths' => [
|
|
resource_path('views'),
|
|
],
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Compiled View Path
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| This option determines where all the compiled Blade templates will be
|
|
| stored for your application. Typically, this is within the storage
|
|
| directory. However, as usual, you are free to change this value.
|
|
|
|
|
*/
|
|
|
|
'compiled' => env(
|
|
'VIEW_COMPILED_PATH',
|
|
realpath(storage_path('framework/views'))
|
|
),
|
|
|
|
];
|