-
-
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
Leading backslash in global namespace #7686
Comments
Hi @norberttech 🙂. It most probably will be fixed with #7679, @mvorisek can you confirm? |
You are correct. #7679 will fix it, hopefully it will be merged soon :) PS: in general, leading backslash in global namespace is not needed, |
Thank you both for your quick response!
I just pretty much want all functions/classes from the global namespace to have the leading backslash without a use statement. I also want to enforce it on a project level so when any contributor does something like |
Bug report
Description
After v3.46.0 CS fixer started removing backslashes from global namespaces,
Which I guess was correct behavior since it wasn't specified, but then after adding:
it worked as expected except few things like for example:
or
which looks like a bug to me.
Runtime version
Used command
Configuration file
Code snippet that reproduces the problem
It can be reproduced on this repo: https://github.com/flow-php/flow
The text was updated successfully, but these errors were encountered: