A representation of a decimal value, such as 2.5. Clients may convert values into language-native decimal formats, such as Java's BigDecimal or Python's decimal.Decimal.
JSON representation
{"value": string}
Fields
value
string
The decimal value, as a string.
The string representation consists of an optional sign, + (U+002B) or - (U+002D), followed by a sequence of zero or more decimal digits ("the integer"), optionally followed by a fraction, optionally followed by an exponent. An empty string should be interpreted as 0.
The fraction consists of a decimal point followed by zero or more decimal digits. The string must contain at least one digit in either the integer or the fraction. The number formed by the sign, the integer and the fraction is referred to as the significand.
The exponent consists of the character e (U+0065) or E (U+0045) followed by one or more decimal digits.
Services should normalize decimal values before storing them by:
Removing an explicitly-provided + sign (+2.5 -> 2.5).
Replacing a zero-length integer value with 0 (.5 -> 0.5).
Coercing the exponent character to upper-case, with explicit sign (2.5e8 -> 2.5E+8).
Removing an explicitly-provided zero exponent (2.5E0 -> 2.5).
Services may perform additional normalization based on its own needs and the internal decimal implementation selected, such as shifting the decimal point and exponent value together (example: 2.5E-1 <-> 0.25). Additionally, services may preserve trailing zeroes in the fraction to indicate increased precision, but are not required to do so.
Note that only the . character is supported to divide the integer and the fraction; ,should not be supported regardless of locale. Additionally, thousand separators should not be supported. If a service does support them, values must be normalized.
Services should clearly document the range of supported values, the maximum supported precision (total number of digits), and, if applicable, the scale (number of digits after the decimal point), as well as how it behaves when receiving out-of-bounds values.
Services may choose to accept values passed as input even when the value has a higher precision or scale than the service supports, and should round the value to fit the supported scale. Alternatively, the service may error with 400 Bad Request (INVALID_ARGUMENT in gRPC) if precision would be lost.
Services should error with 400 Bad Request (INVALID_ARGUMENT in gRPC) if the service receives a value outside of the supported range.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-11-14 UTC."],[[["The JSON representation of a decimal value is a string within a JSON object, formatted as `{ \"value\": string }`."],["The decimal string can include an optional sign, an integer part, a fractional part (using '.' as the decimal separator), and an exponent (using 'e' or 'E')."],["Services are recommended to normalize decimal values by removing explicit '+' signs, handling empty integer values, standardizing the exponent format, and removing zero exponents."],["Services should define and document their supported range, precision, and scale for decimal values, as well as their behavior when receiving out-of-bounds values, which can include rounding or returning an error."],["Thousand separators should not be supported."]]],[]]
