-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Support for complex PHPDoc types in fully_qualified_strict_types
#7619
Labels
kind/feature request
topic/fqcn
Fully Qualified Class Name usage and conversions
topic/phpdoc
PHPDoc tags, Doctrine Annotations etc.
Comments
Related with #5620, all fixes on types must be based on parsed TypeExpression. |
It's not a bug, because initial support for phpDoc was introduced only for simple tags, like |
fully_qualified_strict_types
does not fix callable phpdocfully_qualified_strict_types
This comment has been minimized.
This comment has been minimized.
even unioned ( |
This was referenced Jan 2, 2024
I plan to work on this after #7719 |
This comment was marked as outdated.
This comment was marked as outdated.
This was referenced Jun 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/feature request
topic/fqcn
Fully Qualified Class Name usage and conversions
topic/phpdoc
PHPDoc tags, Doctrine Annotations etc.
Feature request
With the latest release - v3.42.0 - the
fully_qualified_strict_types
rule does fix some phpdoc to imported types, but not all.The following code:
is fixed to:
applied rules: braces_position, no_unused_imports, single_line_empty_body
but I would expect the following result instead:
The text was updated successfully, but these errors were encountered: