Laravel 5.7 Shift

[stefanzweifel]

This pull request includes the changes for upgrading to Laravel 5.7. Feel free to commit any additional changes to the shift-9206 branch.

Before merging, you should:

• Checkout the shift-9206 branch
• Review all pull request comments for additional changes
• Update your dependencies for Laravel 5.6
• Run composer update (if the pre-scripts fail, add --no-scripts)
• Thoroughly test your application

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.

[stefanzweifel]

❌ 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.7 configuration files and merge any changes:

• [x] config/app.php
• [x] config/auth.php
• [x] config/filesystems.php
• [x] config/mail.php
• [x] config/services.php

[stefanzweifel]

ℹ Route::redirect now returns a 302 HTTP status code redirect in Laravel 5.7. Previously it returned a 301. Shift changed these to the new Route::permanentRedirect to preserve your intended behavior. You may want to review these changes if you are using the Route facade outside of the routes folder or want to return a 301.

[stefanzweifel]

ℹ Laravel 5.7 removed the Blade "or" operator in favor of PHP's built-in ?? "null coalesce" operator. Shift automated this change, however, your application may still contain instances of or if you are using Blade syntax outside of the resources folder.

[stefanzweifel]

⚠ Laravel 5.7 was just released. As such, many packages may not yet support Laravel 5.7. Be sure to let the author know. Better yet, submit a pull request as this is often simply a change in their version constraints.

[stefanzweifel]

ℹ Laravel 5.7 removed the resources/assets folder in favor of placing its sub-folders directly under resources. Shift moved these for you automatically. However, you may need to update the paths configured in your frontend build tool (e.g. webpack.mix.js) to reflect this new structure.

While Shift encourages a fully upgraded application, this new structure is not required. If this change significantly impairs your frontend build process, you can revert this commit.

[stefanzweifel]

ℹ Laravel 5.7 now supports email verification when users register for your application. If you have implemented this feature yourself and would like to take advantage of this native functionality, the steps are below. For more details, review the documentation on Email Verification.

• [ ] Add a email_verified_at timestamp column to your User table.
• [ ] Add the VerificationController from Laravel 5.7 to your application.
• [ ] Import the Illuminate\Contracts\Auth\MustVerifyEmail interface in your User model and implement it with the Illuminate\Auth\MustVerifyEmail trait.
• [ ] Listen for the Registered event in your app/Providers/EventServiceProvider per the Laravel 5.7 version.
• [ ] Register the verified middleware in your app/Http/Kernel.php per the Laravel 5.7 version.

[stefanzweifel]

ℹ Shift noticed you have additional namespaces in your project. You should consider using the Consolidate Namespaces Shift to simplify your namespaces into the default Laravel App namespace.