-
Notifications
You must be signed in to change notification settings - Fork 742
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
MissingSummary warning doesn't include filename #1981
Comments
Seems the necessary condition to tickle this bug is a completely empty javadoc stub (i.e. |
copybara-service bot
pushed a commit
that referenced
this issue
Jan 8, 2021
Fixes #1981 PiperOrigin-RevId: 350580163
copybara-service bot
pushed a commit
that referenced
this issue
Jan 8, 2021
Fixes #1981 PiperOrigin-RevId: 350580163
stevie400
pushed a commit
to HubSpot/error-prone
that referenced
this issue
Jan 15, 2021
Fixes google#1981 PiperOrigin-RevId: 350677284
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the problem / feature request:
The MissingSummary warning doesn't include the name of the file that caused the warning.
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
What version of Error Prone are you using?
2.4.0
Expected behavior
The warning should include the name of the file and the relevant line number, if any, just like other warnings from error-prone. E.g.:
The text was updated successfully, but these errors were encountered: