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
Regression on fully_qualified_strict_types
from v3.5 -> v3.6
#6285
Comments
I'm going to close this one in favor of #5199 which describes the need for this behavior with less cognitive load 😉. BTW. This behavior was changed in #6197 (in v3.6.0) with this comment and I am not completely sure if it was a bug that should have been fixed or unfortunate breaking change 🤷♂️. @SpacePossum can you explain why it was changed (if you remember after year and a half 😅)? |
consider this: <?php
namespace B\C {
echo B\Z::Foo;
echo \B\Z::Foo;
}
namespace B\C\B {
class Z {
public const Foo = 1;
}
}
namespace B {
class Z {
public const Foo = 2;
}
} results: so removing the leading |
note that the example in #5199 is very different than this issue and the one linked to my comment, as 5199 shows imports in the root namespace (which is also a far more rare case) |
@SpacePossum do you think this issue should be reopened then? Or maybe we just can add info to the 5199 to handle both scenarios (root and custom namespace)? |
I think the fix that has been done is correct, so if this issue is to be reopened than we need a better example of what is wrong. |
Bug report
fully_qualified_strict_types
no longer removes the FQDN from method parameters as of v3.6.composer.json
src/Api/Bar.php
src/Model/Foo.php
.php-cs-fixer.php
I expected
public function qwe(\FQST\Model\Foo $foo)
to be changed topublic function qwe(Model\Foo $foo)
.This is the behavior seen on v3.5:
results in src/Api/Bar.php
The text was updated successfully, but these errors were encountered: