[javadoc] explain sample values and related classes to improve readability #52
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
amaembo
added a commit
that referenced
this pull request
Oct 6, 2015
[javadoc] explain sample values and related classes to improve readability
|
Merged, thanks |
|
Thanks for your merge! |
sebasjm
pushed a commit
to sebasjm/findbugs
that referenced
this pull request
Mar 11, 2018
…avadoc [javadoc] explain sample values and related classes to improve readability
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a suggestion to help newbies to catch-up FindBugs, by javadoc improvement.
It's good to tell the existence of an utility class
edu.umd.cs.findbugs.util.ClassName, for users of@ SlashedClassNameand@DottedClassName.It's also good to add sample values into javadoc, because it's easier than regexp to understand its format.