-
Notifications
You must be signed in to change notification settings - Fork 79
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
[EC63] UnnecessarilyAssignValuesToVariables rule on caught exception #228
Comments
Hi @natixis-caen, Do you think you can make this correction in a new PR ? if yes, I can be the reviewer if you want. thank you. |
Hi @dedece35 , private class GetVariableVisitor extends BaseTreeVisitor {
@Override
public void visitVariable(VariableTree tree) {
if (!tree.parent().is(Kind.METHOD)) {
variableList.put(tree.simpleName().name(), tree);
}
super.visitVariable(tree);
}
} Any help would be appreciated! |
@natixis-caen, |
Here is the PR: |
Thank you ... do you check de DoD list when a developer contribute ? |
Yes I checked it out and it seems like there's no need. |
Hi @natixis-caen, |
Hello, Did you missed it or am I totally wrong? |
Hi @natixis-caen, i'm ok with this test but I'm talking about this repository : https://github.com/green-code-initiative/ecoCode-java-test-project |
Please, wait for draft #258 |
Hi @natixis-caen, |
Describe the bug
Caught exceptions but not used are analyzed as code smells.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The caught exception should be allowed to be unused.
Software Versions
The text was updated successfully, but these errors were encountered: