-
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
Improve Javadocs for styx-api module #271
Merged
Merged
Changes from 1 commit
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
85effc1
Add javadoc maven plugin and a package-info.java.
mikkokar 7b8e91e
Add package-level api docs for `com.hotels.styx.api`.
mikkokar 242368c
Add javadoc: ContentOverflowException.
mikkokar a1f7ddb
Restrict visibility of FullHttpMessage interface.
mikkokar 5c37db7
A class-level JavaDocs for FullHttpRequest and Response objects.
mikkokar e8145bf
A class-level JavaDocs for HttpRequest and Response objects.
mikkokar 0341513
A JavaDocs for HttpRequest and Response objects.
mikkokar 2077b18
Address code review comments.
mikkokar 7727240
Fix static analysis failures.
mikkokar 1a0f6bc
Improve javadocs for few additional api classes.
mikkokar c7cdd9b
Address code review comments.
mikkokar 73da384
Address code review comments.
mikkokar ec881db
Checkstyle: Allow empty javadoc description.
mikkokar File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The previous text was intended to show that it was the same builder being returned, so that chained calls can be used to set the values. The new text only tells us the type, which we already know.
Is there some builder convention we should be following?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The methods calls can still be chained even if the a new instance was returned.
Whether the builder class is mutable or immutable persistent data structure is an implementation aspect affecting all setter methods. I would describe this in the class level javadoc rather than separately in each method. Like I said it would make no difference to method chaining.
If you feel strongly about this then let's create another issue to specifically improve javadocs for the Builder classes. For now, the priority is to cover the most important gaps in the javadocs, namely 1) the HTTP message API, and (in subsequent PRs) 2) the interceptors API, and 3) application providers.
We haven't agreed on any conventions. Feel free to suggest one.
Is this the only remaining issue that is blocking this PR?