Laravel 5.3 Shift

[hskrasek]

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

Before merging, you should:

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

If you would like more help with your upgrade, check out the human services from Laravel Shift. And if you want to level-up your Git skills, check out Getting Git.

[hskrasek]

❌ I could not upgrade the following core files since they differed from the default Laravel version. You need to compare these configuration files against the Laravel 5.3 versions and merge any changes:

• [x] resources/lang/en/auth.php

[hskrasek]

ℹ Laravel 5.3 no longer includes the app/Events folder by default. It is created for you when you make your first Event using artisan. I did not remove yours as it appears to differ from the default. However, if your app does not use Events, you can remove this folder manually to keep your app streamlined.

[hskrasek]

❌ Laravel 5.3 split the Auth/AuthController.php into the Auth/LoginController.php and the Auth/RegisterController.php. Since yours appears to be customized, I did not remove it. You should compare your Auth/AuthController.php with the newly added controllers and merge your changes accordingly.

[hskrasek]

❌ Laravel 5.3 renamed the Auth/PasswordController.php to Auth/ResetPasswordController.php. Since yours appears to be customized, I did not remove it. You should compare your Auth/PasswordController.php against the added Auth/ResetPasswordController.php and merge your changes accordingly.

[hskrasek]

⚠ If you are using Authentication, you should upgrade any routes using AuthController and PasswordController to use the new authentication controllers. Laravel recommends using the Auth::routes() which registers the proper routes for the new authentication controllers. This method also registers a POST route for /logout instead of a GET route.

[hskrasek]

❌ I was not able to update your app/Providers/AuthServiceProvider.php. You will need to compare yours against the 5.3 version and merge the new changes.

[hskrasek]

❌ I was not able to update your app/Providers/EventServiceProvider.php. You will need to compare yours against the 5.3 version and merge the new changes.

[hskrasek]

❌ I was not able to update your app/Providers/RouteServiceProvider.php. You will need to compare yours against the 5.3 version and merge the new changes.

[hskrasek]

❌ Laravel 5.2 introduced Middleware Groups, which are now used in Laravel 5.3. It appears you have not upgraded to Middleware Groups. You should review Middleware Groups in more detail. Then compare your app/Http/Kernel.php with the 5.3 version and update manually.

[hskrasek]

⚠ Laravel 5.3 now includes a top-level routes folder. In addition, it separates routes into API, console, and web files.I have included a default routes/api.php and routes/console.php as well as migrated your app/Http/routes.php to routes/web.php. You should review your routes to see if they should be separated into one of the new route files.

[hskrasek]

❌ I could not upgrade the following configuration files since they differed from the default Laravel version. You need to compare these configuration files against the Laravel 5.3 configuration files and merge any changes:

• [x] config/database.php
• [x] config/services.php

[hskrasek]

❌ I could not upgrade the following project files since they differed from the default Laravel version. You need to compare these project files against the default Laravel 5.3 versions and merge any changes:

• [x] gulpfile.js
• [x] package.json

[hskrasek]

❌ Laravel 5.3 has a development dependency for symfony/css-selector of 3.1.*. You have a modified dependency for symfony/css-selector in your composer.json. Ensure it meets the new version requirement of 3.1.*.

[hskrasek]

❌ Laravel 5.3 has a development dependency for symfony/dom-crawler of 3.1.*. You have a modified dependency for symfony/dom-crawler in your composer.json. Ensure it meets the new version requirement of 3.1.*.

[hskrasek]

❌ Laravel 5.3 where performs a "loose" comparison. In addition, the strict parameter was removed. If you need to perform a "strict" comparison, you can use whereStrict instead.

You should review the following usages of where to ensure you do not require "strict" compaison:

• [x] app/Http/Controllers/GamersController.php
• [x] app/Http/Controllers/AjaxController.php
• [x] app/Http/Controllers/ClipsController.php
• [x] app/Http/Controllers/ScreenshotController.php

[hskrasek]

❌ The Query Builder returns collections, instead of plain arrays, in Laravel 5.3. You will need to upgrade your code to use collections or chain the all() method onto your query to return a plain array.

You should review the following usages of Query Builder:

• [x] app/Http/Controllers/GamersController.php
• [x] app/Http/Controllers/AjaxController.php
• [x] database/seeds/DatabaseSeeder.php

[hskrasek]

ℹ If you are using Queues, you no longer need to specify the --daemon option when calling the queue:work. This is assumed in Laravel 5.3. Use the --once option to process a single job.

[hskrasek]

ℹ If you are using the database driver for your Queue, you will need to update your jobs and failed_jobs table. Review the Queue section of the Laravel 5.3 Upgrade Guide for more details and feel free to use the migrations from Laravel Shift.

[hskrasek]

ℹ Laravel 5.3 updated several of the default assets as well as adding support for Vue.js. If you are using Laravel to compile assets you may want to review the latest versions of resources/assets/js/app.js and resources/assets/sass/app.scss and update your project accordingly.

[hskrasek]

⚠ Laravel 5.3 added configuration for your application name in config/app.php. Be sure to set this value as it is used in notifications, like the password reset email.

[hskrasek]

ℹ If you have manually upgraded your app for previous versions of Laravel, I recommend running the Laravel Linter to ensure your app is fully upgraded to the latest version of Laravel.