-
-
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
fix: Handle FQCN properly with leading_backslash_in_global_namespace
option enabled
#7654
fix: Handle FQCN properly with leading_backslash_in_global_namespace
option enabled
#7654
Conversation
9605d56
to
6453796
Compare
6453796
to
5bfc669
Compare
@Wirone would you find a moment for review this PR as well - I need it to finish other PRs :) |
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.
As far as I understand the changes, the leading_backslash_in_global_namespace
option was preventing fixer from removing leading \
, but it was not ensuring it's added when missing? Looks good in general, one minor improvement requested.
leading_backslash_in_global_namespace
option enabled
Co-authored-by: Greg Korba <wirone@gmail.com>
ade30d8
to
ff823bd
Compare
…` option enabled (PHP-CS-Fixer#7654) Co-authored-by: Greg Korba <greg@codito.dev>
fix #7648 (comment)