New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Laravel 5.4 Shift #143
Laravel 5.4 Shift #143
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 the [.shiftrc][1] file by using your [PHP CS Fixer][2] config. [1]: https://laravelshift.com/shiftrc-configuration-file [2]: https://github.com/FriendsOfPHP/PHP-CS-Fixer
Laravel 5.1 requires PHP 5.5.9+ which provides the new static `class` property to get the fully qualified name of a class and is preferred over using class name strings.
ℹ️ Laravel 5.4 added new middleware to handle whitespace in request data. This may affect the data your application received. Read this post on Laravel News for more detail to see if you need to modify your application. |
|
❌ Shift could not upgrade the following files since they differed from the default Laravel version. You will need to compare these application files against the default Laravel 5.4 versions and merge any changes:
|
ℹ️ Laravel 5.4 changed the Pusher configuration options |
❌ Shift could not upgrade the following configuration files since they differed from the default Laravel version. You will need to compare these configuration files against the Laravel 5.4 configuration files and merge any changes:
|
❌ The Shift found potential uses of
|
Once you have verified the upgrade, you can use the Laravel 5.4 Tests Shift to upgrade your tests to the new Laravel 5.4 testing layer. |
|
ℹ️ In Laravel 5.4, the date cast creates a Carbon object which calls |
ℹ️ Laravel 5.4 no longer includes the ability to customize the PDO "fetch style". Now |
|
ℹ️ If you are running MySQL prior to version 5.7.7, you may receive a specified key was too long error. You can either upgrade your MySQL or review this post for code to resolve this issue. |
Todo:
|
This pull request includes the changes for upgrading to Laravel 5.4. Feel free to commit any additional changes to the
shift-16542
branch.Before merging, you should:
shift-16542
branchcomposer update
(if the pre-scripts fail, add--no-scripts
)If you want help with your upgrade, check out the Shift Human Services or join the Shifty Coders Slack room to get answers to all your Laravel questions.