public static final class Decimal.Builder extends GeneratedMessageV3.Builder<Decimal.Builder> implements DecimalOrBuilder
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.
[BigDecimal]: https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/math/BigDecimal.html
Protobuf type google.type.Decimal
Inheritance
Object > AbstractMessageLite.Builder<MessageType,BuilderType> > AbstractMessage.Builder<BuilderType> > GeneratedMessageV3.Builder > Decimal.BuilderImplements
DecimalOrBuilderStatic Methods
getDescriptor()
public static final Descriptors.Descriptor getDescriptor()
Returns | |
---|---|
Type | Description |
Descriptor |
Methods
addRepeatedField(Descriptors.FieldDescriptor field, Object value)
public Decimal.Builder addRepeatedField(Descriptors.FieldDescriptor field, Object value)
Parameters | |
---|---|
Name | Description |
field |
FieldDescriptor |
value |
Object |
Returns | |
---|---|
Type | Description |
Decimal.Builder |
build()
public Decimal build()
Returns | |
---|---|
Type | Description |
Decimal |
buildPartial()
public Decimal buildPartial()
Returns | |
---|---|
Type | Description |
Decimal |
clear()
public Decimal.Builder clear()
Returns | |
---|---|
Type | Description |
Decimal.Builder |
clearField(Descriptors.FieldDescriptor field)
public Decimal.Builder clearField(Descriptors.FieldDescriptor field)
Parameter | |
---|---|
Name | Description |
field |
FieldDescriptor |
Returns | |
---|---|
Type | Description |
Decimal.Builder |
clearOneof(Descriptors.OneofDescriptor oneof)
public Decimal.Builder clearOneof(Descriptors.OneofDescriptor oneof)
Parameter | |
---|---|
Name | Description |
oneof |
OneofDescriptor |
Returns | |
---|---|
Type | Description |
Decimal.Builder |
clearValue()
public Decimal.Builder clearValue()
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.
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 lower-case (
2.5E8
->2.5e8
). 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.The ENBF grammar is:
DecimalString = [Sign] Significand [Exponent];
Sign = '+' | '-';
Significand = Digits ['.'] [Digits] | [Digits] '.' Digits;
Exponent = ('e' | 'E') [Sign] Digits;
Digits = { '0' | '1' | '2' | '3' | '4' | '5' | '6' | '7' | '8' | '9' };
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.
string value = 1;
Returns | |
---|---|
Type | Description |
Decimal.Builder |
This builder for chaining. |
clone()
public Decimal.Builder clone()
Returns | |
---|---|
Type | Description |
Decimal.Builder |
getDefaultInstanceForType()
public Decimal getDefaultInstanceForType()
Returns | |
---|---|
Type | Description |
Decimal |
getDescriptorForType()
public Descriptors.Descriptor getDescriptorForType()
Returns | |
---|---|
Type | Description |
Descriptor |
getValue()
public String getValue()
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.
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 lower-case (
2.5E8
->2.5e8
). 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.The ENBF grammar is:
DecimalString = [Sign] Significand [Exponent];
Sign = '+' | '-';
Significand = Digits ['.'] [Digits] | [Digits] '.' Digits;
Exponent = ('e' | 'E') [Sign] Digits;
Digits = { '0' | '1' | '2' | '3' | '4' | '5' | '6' | '7' | '8' | '9' };
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.
string value = 1;
Returns | |
---|---|
Type | Description |
String |
The value. |
getValueBytes()
public ByteString getValueBytes()
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.
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 lower-case (
2.5E8
->2.5e8
). 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.The ENBF grammar is:
DecimalString = [Sign] Significand [Exponent];
Sign = '+' | '-';
Significand = Digits ['.'] [Digits] | [Digits] '.' Digits;
Exponent = ('e' | 'E') [Sign] Digits;
Digits = { '0' | '1' | '2' | '3' | '4' | '5' | '6' | '7' | '8' | '9' };
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.
string value = 1;
Returns | |
---|---|
Type | Description |
ByteString |
The bytes for value. |
internalGetFieldAccessorTable()
protected GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
Returns | |
---|---|
Type | Description |
FieldAccessorTable |
isInitialized()
public final boolean isInitialized()
Returns | |
---|---|
Type | Description |
boolean |
mergeFrom(CodedInputStream input, ExtensionRegistryLite extensionRegistry)
public Decimal.Builder mergeFrom(CodedInputStream input, ExtensionRegistryLite extensionRegistry)
Parameters | |
---|---|
Name | Description |
input |
CodedInputStream |
extensionRegistry |
ExtensionRegistryLite |
Returns | |
---|---|
Type | Description |
Decimal.Builder |
Exceptions | |
---|---|
Type | Description |
IOException |
mergeFrom(Message other)
public Decimal.Builder mergeFrom(Message other)
Parameter | |
---|---|
Name | Description |
other |
Message |
Returns | |
---|---|
Type | Description |
Decimal.Builder |
mergeFrom(Decimal other)
public Decimal.Builder mergeFrom(Decimal other)
Parameter | |
---|---|
Name | Description |
other |
Decimal |
Returns | |
---|---|
Type | Description |
Decimal.Builder |
mergeUnknownFields(UnknownFieldSet unknownFields)
public final Decimal.Builder mergeUnknownFields(UnknownFieldSet unknownFields)
Parameter | |
---|---|
Name | Description |
unknownFields |
UnknownFieldSet |
Returns | |
---|---|
Type | Description |
Decimal.Builder |
setField(Descriptors.FieldDescriptor field, Object value)
public Decimal.Builder setField(Descriptors.FieldDescriptor field, Object value)
Parameters | |
---|---|
Name | Description |
field |
FieldDescriptor |
value |
Object |
Returns | |
---|---|
Type | Description |
Decimal.Builder |
setRepeatedField(Descriptors.FieldDescriptor field, int index, Object value)
public Decimal.Builder setRepeatedField(Descriptors.FieldDescriptor field, int index, Object value)
Parameters | |
---|---|
Name | Description |
field |
FieldDescriptor |
index |
int |
value |
Object |
Returns | |
---|---|
Type | Description |
Decimal.Builder |
setUnknownFields(UnknownFieldSet unknownFields)
public final Decimal.Builder setUnknownFields(UnknownFieldSet unknownFields)
Parameter | |
---|---|
Name | Description |
unknownFields |
UnknownFieldSet |
Returns | |
---|---|
Type | Description |
Decimal.Builder |
setValue(String value)
public Decimal.Builder setValue(String value)
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.
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 lower-case (
2.5E8
->2.5e8
). 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.The ENBF grammar is:
DecimalString = [Sign] Significand [Exponent];
Sign = '+' | '-';
Significand = Digits ['.'] [Digits] | [Digits] '.' Digits;
Exponent = ('e' | 'E') [Sign] Digits;
Digits = { '0' | '1' | '2' | '3' | '4' | '5' | '6' | '7' | '8' | '9' };
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.
string value = 1;
Parameter | |
---|---|
Name | Description |
value |
String The value to set. |
Returns | |
---|---|
Type | Description |
Decimal.Builder |
This builder for chaining. |
setValueBytes(ByteString value)
public Decimal.Builder setValueBytes(ByteString value)
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.
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 lower-case (
2.5E8
->2.5e8
). 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.The ENBF grammar is:
DecimalString = [Sign] Significand [Exponent];
Sign = '+' | '-';
Significand = Digits ['.'] [Digits] | [Digits] '.' Digits;
Exponent = ('e' | 'E') [Sign] Digits;
Digits = { '0' | '1' | '2' | '3' | '4' | '5' | '6' | '7' | '8' | '9' };
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.
string value = 1;
Parameter | |
---|---|
Name | Description |
value |
ByteString The bytes for value to set. |
Returns | |
---|---|
Type | Description |
Decimal.Builder |
This builder for chaining. |