Laravel 6.0 Shift #11
Conversation
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 through by using your [PHP CS Fixer][1] config within 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
Laravel 5 adopted the short array syntax which became available in PHP 5.4.
Laravel recommends using the `Str` and `Arr` class methods directly instead of the respective helper functions. These helper functions are [deprecated in Laravel 5.8][1] and will be removed in a future version. [1]: laravel/framework#26898
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.
|
|
|
ℹ️ Laravel 6.0 changed the default Redis client from However, if possible, consider switching to phpredis to gain the performance of its PHP extension and avoid using the deprecated |
|
ℹ️ The Eloquent model's |
|
ℹ️ Laravel 6.0 made performance optimizations for integer key types. If you are using a string as your model's primary key, you may set the /**
* The "type" of the primary key ID.
*
* @var string
*/
protected $keyType = 'string'; |
|
ℹ️ The |
|
ℹ️ Previous versions of Laravel would retry jobs indefinitely. Beginning with Laravel 6.0, the |
|
🎉 Congratulations, you're now running the latest version of Laravel. The following Shifts can ensure your app is fully upgraded and following the practices recommended by Laravel and the community:
In addition, stay upgraded forever as well as run these Shifts by subscribing to one of the new Shifty Plans. |
This pull request includes the changes for upgrading to Laravel 6.0. Feel free to commit any additional changes to the
shift-19019branch.Before merging, you need to:
shift-19019branchcomposer update(if the scripts fail, add--no-scripts)If you need help with your upgrade, check out the Human Shifts. You may also join the Shifty Coders Slack workspace to level-up your Laravel skills.