Skip to content

Editorial: Fix the described value type of unit conversion results - #145

Open
jessealama wants to merge 1 commit into
mainfrom
convertto-value-type-consistency
Open

Editorial: Fix the described value type of unit conversion results#145
jessealama wants to merge 1 commit into
mainfrom
convertto-value-type-consistency

Conversation

@jessealama

Copy link
Copy Markdown
Collaborator

The Introduction and the note on the value getter both stated that unit
conversion always stores a decimal digit string for finite values. That
stopped being true in #103, which made .convertTo produce a Number unless
fractionDigits or significantDigits is supplied, matching the README
change in #101.

The note on the value getter was also incomplete in a second way: it did
not mention that an Amount constructed from a String holds a String
value even when no precision options are given.

The Introduction and the note on the value getter both stated that unit
conversion always stores a decimal digit string for finite values. That
stopped being true in #103, which made `.convertTo` produce a Number unless
`fractionDigits` or `significantDigits` is supplied, matching the README
change in #101.

The note on the value getter was also incomplete in a second way: it did
not mention that an Amount constructed from a String holds a String
value even when no precision options are given.
@github-actions

Copy link
Copy Markdown
PR Preview Action v1.8.1

QR code for preview link

🚀 View preview at
https://tc39.github.io/proposal-amount/pr-preview/pr-145/

Built to branch gh-pages at 2026-08-11 15:37 UTC.
Preview will be ready when the GitHub Pages deployment is complete.

@jessealama
jessealama requested a review from eemeli August 11, 2026 15:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants