feat: create new SafeDeclareStrictTypesRector #7814
+1,031
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello!
Motivation
See https://x.com/VotrubaT/status/2008248184540418398
Currently, the
DeclareStrictTypesRectorjust indiscriminately addsdeclare(strict_types=1)to all files. However:This PR creates a new rule (
SafeDeclareStrictTypesRector) that is (should be) completely safe and only adds strict types to the file when it won't break code. I've also added it to thecodeQualityruleset (but let me know if you'd rather it go elsewhere).Implementation
Basically, strict_types only affects calling code and prevents scalar type coercion in the following cases:
CallLikes andAttributesFunctionLikesThis PR adds a new service class (
StrictTypeSafetyChecker) that iterates through all the above and checks the type compatibility. If the file is completely safe then the refactor is performed, otherwise the file is skipped. I conservatively skip files when we can't be sure (e.g., dynamic calls, unpacks, etc.).All of the actual type checking is deferred to phpstan's
Type::accepts($type, strictTypes: true)api which really makes things clean on our end.CC: @TomasVotruba
Thanks!