-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
Extract no type @param
annotation with PhpStanExtractor
#59924
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
Conversation
thomasdubuffet
commented
Mar 6, 2025
•
edited
Loading
edited
Q | A |
---|---|
Branch? | 7.2 |
Bug fix? | yes |
New feature? | no |
Deprecations? | no |
Issues | Fix #59923 |
License | MIT |
Hey! I see that this is your first PR. That is great! Welcome! Symfony has a contribution guide which I suggest you to read. In short:
Review the GitHub status checks of your pull request and try to solve the reported issues. If some tests are failing, try to see if they are failing because of this change. When two Symfony core team members approve this change, it will be merged and you will become an official Symfony contributor! I am going to sit back now and wait for the reviews. Cheers! Carsonbot |
@param
annotation with PhpStanExtractor
@param
annotation with PhpStanExtractor
Hey @thomasdubuffet, thanks for taking care of this! The issue seems to be there as well in 6.4, could you instead target the 6.4 branch please? |
Unless I am mistaken, there is no |
My bad, didn't notice that |
@param
annotation with PhpStanExtractor
@param
annotation with PhpStanExtractor
src/Symfony/Component/PropertyInfo/Extractor/PhpStanExtractor.php
Outdated
Show resolved
Hide resolved
f5e493d
to
0d6cc80
Compare
0d6cc80
to
03372e8
Compare
Thank you @thomasdubuffet. |