Add missing javadoc for User API classes #203
Merged
Conversation
This file contains hidden or 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
kpalang
requested review from
a team,
gibson9583,
kayyagari,
kpalang and
pacmano1
and removed request for
a team
kpalang
approved these changes
Nov 15, 2025
mgaffigan
approved these changes
Nov 15, 2025
Signed-off-by: Tony Germano <tony@germano.name>
tonygermano
force-pushed
the
maint/add-missing-javadoc
branch
from
c05e3fb to
d934af2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Separated from #200 and #146
Several of the User API classes were lacking complete javadoc comments, which was triggering some warnings during build. Of course it is useful to have these, which is why it was warning in the first place.