PHPStan rule to forbid dynamic object instantiation #19877
Closed
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.
Checklist before requesting a review
Description
Instanciating new objects using a dynamic value can cause unexpected issues.
CommonDBTM
class, and execute an unexpected code sequence (see 3b6bc1b).I propose to add a PHPStan rule to detect and consider as errors these dynamic objects instantiations.
For the moment, the detected errors are not fixed. We could either try to fix them in this PR, or add them to the baseline and fix them later, or even use this rule to detect errors and fix them in separated PRs, and wait to be sure that there is no false positive issues before merging this PR.
Here is the test file I used to validate this rule:
and the corresponding results: