-
Notifications
You must be signed in to change notification settings - Fork 15
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 Linter Shift #19
base: master
Are you sure you want to change the base?
Conversation
The Laravel framework adopts the PSR-2 coding style in version 5.1. Laravel apps *should* adopt this coding style as well. Read the [PSR-2 coding style guide][1] for more details and check out [PHPCS][2] to use as a code formatting tool. [1]: https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-guide.md [2]: https://github.com/squizlabs/PHP_CodeSniffer
Since Laravel 5.1 requires PHP 5.5.9+ using the *new* static `class` property to get the fully qualified name of a class is preferred over using class name strings.
⚠ Your Laravel framework dependency is not set to the latest version in Composer. Unless you have a requirement for using a specific version of Laravel, you should set this to |
ℹ Your Laravel version is less than the latest version (5.3). Use Laravel Shift to not only upgrade your project to the latest version of Laravel, but resolve most of the lint detected here. |
❌ Your
|
❌ Your
|
❌ Your |
⚠ Laravel 5.3 streamlined the
|
❌ Laravel 5.3 now includes a top-level |
❌ I found files using the
|
⚠ It appears your User model does not extend |
❌ Laravel 5.3 replaced
|
⚠ Your |
⚠ Your |
⚠ Your |
⚠ Your |
❌ The following configuration files differ from the 5.3 defaults. If you are modifying configuration values directly, you should consider using an environment variable instead. You should compare your configuration files against the Laravel 5.3 configuration files and make any updates.
|
This pull request contains code changes and comments for code detected as incompatible or unrecommended by the Laravel Linter. You should review each comment and commit changes to the
laravel-linter-shift
branch before merging.If there were items you feel could have been detected, please leave a comment on this pull request to help improve Laravel Shift.