-
-
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
[RFC] var_dump/dump fixer #2195
Comments
Hi and thanks for your suggestion :) How about |
@SpacePossum thank you for your feedback. I agree with you that such a functionality might be out of scope of the project. Right now I can't judge what is more risky for developer - keeping statements in the code, which are commonly used for debugging (especially taking into account that i.e. However, I think that contrib fixers are usually enabled explicitly by developer, which means that one understands all the consequences of it. Anyway, the reason why I've created the issue is that I've already done this fixer for private purposes. If community wants to have that, I will be more than happy to contribute to an awesome tool. If there is no need/it is our of scope of the project, I will just use my fork. |
Also consider that those debug statements, especially |
Short summary from PR discussion - too risky to have it in core. For those, who want to have that - https://github.com/akovalyov/DebugStatementsFixers. |
This RFC is for var_dump/dump removal fixer. While a lot of devs debug via var_dump(or via Symfony/VarDumper dump), it is dangerous to have it in code, especially if it appears in production . So, why not to introduce these functions removal? What do you think?
The text was updated successfully, but these errors were encountered: