Laravel 7.x Shift #778
Laravel 7.x Shift #778
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 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
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 7 upgraded to Symfony 5 which passes instances of the Shift automated this change. However, if you receive a |
|
ℹ️ Laravel 7 moved the Authentication components into a separate Shift added this dependency for convenience. However, if you do not plan to use the Authentication components, you may remove this dependency as well as the |
|
ℹ️ Shift updated your These are related to the underlying Symfony 5 updates. You may change them if you are familiar with these options. |
|
Shift attempted to automation this change, but you should review any additional environment configuration and update to the new variable name. |
|
If you have a lot of customizations, you may quickly undo this commit with
|
|
ℹ️ Shift updated your dependencies for Laravel 7. While many of the popular packages are reviewed, you may have to update additional packages in order for your application to be compatible with Laravel 7. Watch dealing with dependencies for tips on handling package incompatibilities. |
|
ℹ️ Laravel 7 removed some of the PHPUnit configuration in favor of the defaults. While this is not a required changed, it is a good opportunity to compare your |
|
This does not affect how dates are stored. Only how they are serialized when using the If you need to preserve the previous format, you may override the |
|
ℹ️ All of the underlying Symfony components used by Laravel have been upgraded to Symfony 5. If you are directly interacting with Symfony components, you should review the Symfony change log for additional changes. |
|
ℹ️ Shift noticed you have additional namespaces in your application. You should consider using the Consolidate Namespaces Shift to simplify your namespaces into the default Laravel |
|
🎉 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. |
|
Would love to know if there us a time frame for moving to Laravel 7, and where things are at? What is needed to help complete this that we can help with? |
This pull request includes the changes for upgrading to Laravel 7.x. Feel free to commit any additional changes to the
shift-25927branch.Before merging, you need to:
shift-25927branchcomposer 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.