-
Notifications
You must be signed in to change notification settings - Fork 6.1k
JDK-6503196: API doc for DecimalFormat::getMaximumIntegerDigits is unclear #17541
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
Conversation
👋 Welcome back jlu! A progress list of the required criteria for merging this PR into |
@justin-curtis-lu The following labels will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command. |
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
@justin-curtis-lu 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 60 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 |
/integrate |
Going to push as commit 3d32c46.
Your commit was automatically rebased without conflicts. |
@justin-curtis-lu Pushed as commit 3d32c46. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Please review this PR which clarifies some confusion for the digit getter and setter methods of DecimalFormat.
When formatting non
BigInteger
andBigDecimal
values, DecimalFormat uses 309/340 as hard limits for integer and fraction digit limits, regardless of the value set by the user. There was some confusion, that those numbers might be returned by the getters, when in reality, they are only used internally.Moving the 309/340 wording to the class description and linking to it reduces the repetitive wording, but also eliminates the confusion that the getters may return those values. This should be OK, as setting limits higher than those values are likely rare, so the warning does not need to be in every method description.
Additionally,
getMaximumIntegerDigits()
is updated to point to the patterns section to warn about the non-obvious rules for max integer digits.Progress
Issues
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/17541/head:pull/17541
$ git checkout pull/17541
Update a local copy of the PR:
$ git checkout pull/17541
$ git pull https://git.openjdk.org/jdk.git pull/17541/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 17541
View PR using the GUI difftool:
$ git pr show -t 17541
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/17541.diff
Webrev
Link to Webrev Comment