-
Notifications
You must be signed in to change notification settings - Fork 4
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
IBX-8138: [Rector] Applied rules from Symfony 5 Rector set lists #51
Conversation
Applied rules: * AddReturnTypeDeclarationRector * RenameClassConstFetchRector * ResponseStatusCodeRector
Applied rules: * ResponseStatusCodeRector
Applied rules: * RenameClassConstFetchRector
Quality Gate passedIssues Measures |
@@ -4,17 +4,18 @@ | |||
* @copyright Copyright (C) Ibexa AS. All rights reserved. | |||
* @license For full copyright and license information view LICENSE file distributed with this source code. | |||
*/ | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess it's not covered by existing Rector rules, but would be good to add declare(strict_types=1);
whenever possible as we touch such amount of codebase...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
strict_types
do have an effect on the execution, so we'd want this done in more controlled fashion than just adding it everywhere.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
whenever possible
I am not talking about introducing a specific rector, but decreasing amount of code to touch on our way to Sf6 whenever a low-hanging fruit kind of situation presents itself.
Description:
Applied rules from Symfony 5 Rector set lists.
For QA:
No QA needed. Regression tests should be enough.
Documentation:
This is code refactoring without behavior change. No documentation changes needed.