-
Notifications
You must be signed in to change notification settings - Fork 32
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
Unreachable code error not shown #37
Comments
Yes it would be really helpful to see these kinds of errors. |
Hi, |
Thank youl. I don't know if the regexp is the same but, the vet errors should be added:
Thank you for your kind support |
Can you test this solution for resolve the problem with the rules unreachable code? |
I just tested it. It worked fine. I have the "unreachable code" in the sonar report. Thank you. Let me know if I can support you for adding other errors. Kind regards |
@Cosby86 could you close the issue now that the problem is fixed? |
Hi danielle I'm waiting for the other errors support:
Are those errors already implemented? |
@thibaultfalque could we add the above vet errors in the plugin to close that issue? |
hi @Cosby86 and @danielleberre the first and the last error are present (0046571). I will add the other rules but I don't find the rules in vet page (https://golang.org/cmd/vet/). |
Hello,
I've the following gometalinter entry in my gometalinter's report:
<error column="0" line="93" message="unreachable code" severity="error" source="vet"></error>
but this isn't shown in sonar.
Can you kindly add this rule?
The text was updated successfully, but these errors were encountered: