Laravel 5.7 Shift - Githubissues

langleyfoxall / laravel-boilerplate

Boilerplate for Laravel with common tools/plugins for ease of development.

MIT License

2 stars 4 forks source link

Laravel 5.7 Shift #7

Closed AlexCatch closed 5 years ago

AlexCatch commented 6 years ago

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

Before merging, you should:

Checkout the shift-9384 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.

AlexCatch commented 6 years ago

❌ 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

AlexCatch commented 6 years ago

ℹ 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.

AlexCatch commented 6 years ago

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

AlexCatch commented 6 years ago

ℹ 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.

AlexCatch commented 6 years ago

ℹ 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.

[x] Add a email_verified_at timestamp column to your User table.
[x] Add the VerificationController from Laravel 5.7 to your application.
[x] Import the Illuminate\Contracts\Auth\MustVerifyEmail interface in your User model and implement it with the Illuminate\Auth\MustVerifyEmail trait.
[x] 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.