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
fix: Several improvements for fully_qualified_strict_types
(respect declared symbols, relative imports, leading backslash in global namespace)
#7679
Conversation
a8a4192
to
8da3b68
Compare
That's a major refactor, I took a quick look and I am excited about how it works now, but I need more time to wrap my head around it. Anyway, huge work 👏! |
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.
Ooooffff, that was tough. It's probably not a complete review, but I would like to discuss some things so treat it like an early feedback. I am also kind of open for merging this as-is (after fixing clear problems, obviously) because previously it was also merged in non-optimal form just to provide more coverage. This PR solves so many issues that I think it's worth it even if we would need to continue refactoring later 🙂.
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.
I believe this needs to be done, that's why I'm re-marking PR as "changes requested".
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.
fully_qualified_strict_types
must honor implicitly imported short namesfully_qualified_strict_types
(respect declared symbols, relative imports, leading backslash in global namespace)
Thank you @mvorisek veeeeeeeeeery much for this, huge work 🍻!! |
@Wirone, thank you! ❤ |
… declared symbols, relative imports, leading backslash in global namespace) (PHP-CS-Fixer#7679)
fix #5199
fix #7642 (and #7677 duplicate)
fix #7680
fix #7686