-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
8175709: DateTimeFormatterBuilder.appendZoneId() has misleading JavaDoc #22837
8175709: DateTimeFormatterBuilder.appendZoneId() has misleading JavaDoc #22837
Conversation
👋 Welcome back naoto! A progress list of the required criteria for merging this PR into |
@naotoj This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 96 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
Webrevs
|
* If the parse starts with '+' or '-', then the parser expects an | ||
* offset-based zone and will not match region-based zones. The offset | ||
* ID parsing is equivalent to using {@link #appendOffset(String, String)} | ||
* using the arguments 'HH:MM:ss' and the no offset string '0'. |
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 change to drop UT, UTC, GMT, from offset parsing, looks to be correct.
However, it does accept parsing of the offset formatted strings in contradiction to the 2nd paragraph above.
* This appends an instruction to format/parse the zone ID to the builder
* only if it is a region-based ID.
This pre-existing text is also isn't clear in that the formatter is always appended to the builder.
The accepting only of a region-based ID occurs when the DateTimeFormatter.parse(...) is parsing.
Perhaps a separate clarification may be useful
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.
Thanks, Roger. Updated the description per your suggestion.
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.
lgtm
Thanks for the review! |
Going to push as commit 9702acc.
Your commit was automatically rebased without conflicts. |
Clarifying the documentation of
DateTimeFormatterBuilder.appendZoneId()
and similar methods to align the description with the behavior, in whichZoneOffset
is only parsed from the formatter for offset texts without any prefixes. Corresponding CSR has also been drafted.Progress
Issues
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/22837/head:pull/22837
$ git checkout pull/22837
Update a local copy of the PR:
$ git checkout pull/22837
$ git pull https://git.openjdk.org/jdk.git pull/22837/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 22837
View PR using the GUI difftool:
$ git pr show -t 22837
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/22837.diff
Using Webrev
Link to Webrev Comment