StdLocalizationParam
This structure holds a single message parameter and formatting settings for it. The structure has fields for string, long, double, date time and nested messages. Only one will be used depending on the type of data sent. For date, double and long it is possible to set additional formatting details.
Properties
The double value associated with the parameter. The number of displayed fractional digits is changed via LocalizationParam.precision field. this field will be set when double value is used.
Date and time value associated with the parameter. Use the LocalizationParam.format field to specify date and time display style. this field will be set when date and time value is used.
The LocalizationParam.DateTimeFormat enumerated type lists possible date and time formatting options. It combines the Unicode CLDR format types - full, long, medium and short with 3 different presentations - date only, time only and combined date and time presentation.
SHORT_DATE : The date and time value will be formatted as short date, for example 2019-01-28
MED_DATE : The date and time value will be formatted as medium date, for example 2019 Jan 28
LONG_DATE : The date and time value will be formatted as long date, for example 2019 Jan 28
FULL_DATE : The date and time value will be formatted as full date, for example 2019 Jan 28, Mon
SHORT_TIME : The date and time value will be formatted as short time, for example 12:59
MED_TIME : The date and time value will be formatted as medium time, for example 12:59:01
LONG_TIME : The date and time value will be formatted as long time, for example 12:59:01 Z
FULL_TIME : The date and time value will be formatted as full time, for example 12:59:01 Z
SHORT_DATE_TIME : The date and time value will be formatted as short date and time, for example 2019-01-28 12:59
MED_DATE_TIME : The date and time value will be formatted as medium date and time, for example 2019 Jan 28 12:59:01
LONG_DATE_TIME : The date and time value will be formatted as long date and time, for example 2019 Jan 28 12:59:01 Z
FULL_DATE_TIME : The date and time value will be formatted as full date and time, for example 2019 Jan 28, Mon 12:59:01 Z
Possible values are: SHORT_DATE , MED_DATE , LONG_DATE , FULL_DATE , SHORT_TIME , MED_TIME , LONG_TIME , FULL_TIME , SHORT_DATE_TIME , MED_DATE_TIME , LONG_DATE_TIME , FULL_DATE_TIME
long value associated with the parameter. this field will be set when long value is used.
Nested localizable value associated with the parameter. This is useful construct to convert to human readable localized form enumerated type and boolean values. It can also be used for proper handling of pluralization and gender forms in localization. Recursive NestedLocalizableMessage instances can be used for localizing short lists of items. this field will be set when nested localization message value is used.
Number of fractional digits to include in formatted double value. this will be set when exact precision is required for rendering double numbers.
String value associated with the parameter. this field will be set when string value is used.
JSON Example
{
"d": 0,
"dt": "string",
"format": "SHORT_DATE",
"i": 0,
"l": {
"id": "string",
"params": "StdLocalizationParam Object"
},
"precision": 0,
"s": "string"
}
Dependency Chain.
To identify where the loop occurs in your dependency chain, check below.
Std_LocalizationParam
Automated code generation tools, may produce unexpected results because of this.
