-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
magento/magento2#22317: CodeSniffer should not mark correctly aligned DocBlock elements as code style violation. #22321
magento/magento2#22317: CodeSniffer should not mark correctly aligned DocBlock elements as code style violation. #22321
Conversation
Hi @p-bystritsky. Thank you for your contribution
For more details, please, review the Magento Contributor Assistant documentation |
… elements as code style violation.
b7dd9e6
to
bed152b
Compare
* @param File $phpcsFile | ||
* @param array $paramPointers | ||
* | ||
* @see https://devdocs.magento.com/guides/v2.3/coding-standards/docblock-standard-general.html#format-consistency |
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.
Omg, didn't even know we have such a dumb rule O.o
@p-bystritsky did you align such changes with @lenaorobei or @paliarush? I believe there should be some plan elaborated in regards to annotation sniffs as current ones are pretty lame, probably there is no need to try improve them sporadically. |
Hi @p-bystritsky! The idea is to implement proper DocBlock checking sniffs and remove Annotations sniffs from Magento at all. Here are related tasks: magento/magento-coding-standard#58 and magento/magento-coding-standard#54 I did not merge those Annotations sniffs to the consolidated Coding Standard, because they produce false-positive findings. |
@lenaorobei should we merge this pull request to improve the existing sniffs until the DocBlock checking is in progress? |
@sivaschenko I don't see any reasons to not to merge, since it improves developer experience. |
Hi @sivaschenko, thank you for the review. |
Hi @p-bystritsky, thank you for your contribution! |
…cBlock elements as code style violation. #22321
Description (*)
Fixed Issues (if relevant)
Manual testing scenarios (*)
Contribution checklist (*)