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
Unused use statement rule #801
Comments
Nope. For a questions you can use our Gitter channel: https://gitter.im/squizlabs/PHP_CodeSniffer |
There is a sniff for that in Drupal's coder: https://www.drupal.org/project/coder |
I just wanted this feature and was considering writing my own sniff. @klausi, as the owner of coder would you have any objection to PHPCS nicking the UnusedUseStatementSniff and putting it into the (If you're okay with it, I'm also interested to look over coder for other non-Drupal-specific sniffs that could happily live in PHPCS and start migrating them. It looks like you've got a lot of cool stuff over there!) |
Coder is GPLv2+ licensed and PHPCS is MIT, so you need to get copyright permission from all authors of a sniff when you want to pull in sniffs from Coder to PHPCS for MIT relicensing. Which is totally fine with me, so you have my permission to do that. In the case of UnusedUseStatementSniff we also need to ask @alexpott (the only other author). |
Fine by me. |
Looks like @alexpott agreed, can it be included? |
Alread in |
I think this issue can be closed. Or is it still in disucssion? :) |
Is there a rule to detect unused use statements? For example:
PHP-CS-Fixer has an
unused_use
fixer but I'd prefer to use the one tool if possible.The text was updated successfully, but these errors were encountered: