enhance: Add TARGET_PARAMETER to Attribute for improved Validation #523
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.
Overview
This PR improves the attribute declaration in our classes by allowing annotations to be used on both properties and parameters. This enhancement provides additional flexibility in our coding practices, particularly for validation purposes.
Details
Previously, our attribute declaration only targeted properties, like so:
#[Attribute(Attribute::TARGET_PROPERTY)]
. This way of declaring attributes was missing an important aspect: validation via constructor parameters.In cases where annotations were used in the constructor for parameters, PHPStan would throw an error, considering that the corresponding annotation doesn't have the appropriate rights to be used on parameters.
To resolve this issue and to increase the adaptability of our code, we have updated the attribute declaration:
#[Attribute(Attribute::TARGET_PROPERTY | Attribute::TARGET_PARAMETER)]
. This allows the use of annotations on parameters as well.Impact
This change will help us:
Error Example
My PHP code
My PHPStan Configration
Error Images
We believe this update will greatly aid in maintaining clean, secure, and efficient code. As always, any feedback is welcome. Please review and let me know your thoughts.