You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If details.total.amount.value is not a valid decimal monetary value, then throw a TypeError.
If the first character of details.total.amount.value is U+002D HYPHEN-MINUS, then throw a TypeError. total must be a non-negative amount.
We should just define a "valid non-negative monetary value" as an algorithm that calls into "valid decimal monetary value".
The text was updated successfully, but these errors were encountered:
marcoscaceres
changed the title
PaymentRequest type checks
PaymentRequest type checks (valid non-negative currency value)
Nov 14, 2016
marcoscaceres
changed the title
PaymentRequest type checks (valid non-negative currency value)
PaymentRequest type checks (valid non-negative monetary value)
Nov 14, 2016
I don't mind this. However, if we do this we need to ensure that the relevant prose is preserved. We often (in specs) err on the side of a well expressed algorithm at the expense of its readability by mere mortals.
The following should be combined:
We should just define a "valid non-negative monetary value" as an algorithm that calls into "valid decimal monetary value".
The text was updated successfully, but these errors were encountered: