-
-
Notifications
You must be signed in to change notification settings - Fork 7
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 #2230
base: 2214-php-laravel-upgrade
Are you sure you want to change the base?
Laravel Linter #2230
Conversation
|
❌ The following configuration files differ from the Laravel defaults. If you are modifying configuration values directly, consider using an environment variable instead to keep these files maintainable. You should compare your configuration files against the latest version and merge any updates.
|
|
ℹ️ Starting with Laravel 8, the |
While global references are allowed through aliases, you should import the facade explicitly. This can improve clarity not only for developers, but static analysis used by your IDE.
|
|
|
|
|
|
|
ℹ️ Shift detected legacy model factories. Laravel 8 introduced class based model factories. You may automate the conversion to class based model factories using the Shift Workbench. |
❌ Laravel 10 added PHP type hints to all user-land code included in a new Laravel application. Shift detected these files are missing type hints. Shift recommends adding them to align with the latest Laravel conventions. You may automate this process by running the Laravel Type Hints task within Shift Workbench. |
The following PHP files are missing a namespace:
|
|
ℹ️ As noted, much of the lint detected above can be automatically fixed using the Laravel Fixer. Save yourself time and clean up your codebase quickly with this new Shift. |
This pull request includes changes and recommendations for crafting your application "The Laravel Way". Feel free to commit any additional changes to the
shift-110970
branch.Before merging, you need to:
shift-110970
branchMuch of the lint detected may be automatically fixed by running the Laravel Fixer or tasks within the Shift Workbench.