package google.type

Get desktop application:
View/edit binary Protocol Buffers messages

Represents civil time (or occasionally physical time). This type can represent a civil time in one of a few possible ways: * When utc_offset is set and time_zone is unset: a civil time on a calendar day with a particular offset from UTC. * When time_zone is set and utc_offset is unset: a civil time on a calendar day in a particular time zone. * When neither time_zone nor utc_offset is set: a civil time on a calendar day in local time. The date is relative to the Proleptic Gregorian Calendar. If year is 0, the DateTime is considered not to have a specific year. month and day must have valid, non-zero values. This type may also be used to represent a physical time if all the date and time fields are set and either case of the `time_offset` oneof is set. Consider using `Timestamp` message for physical time instead. If your use case also would like to store the user's timezone, that can be done in another field. This type is more flexible than some applications may want. Make sure to document and validate your application's limitations.

• int32 year = 1

  Optional. Year of date. Must be from 1 to 9999, or 0 if specifying a datetime without a year.

• int32 month = 2

  Required. Month of year. Must be from 1 to 12.

• int32 day = 3

  Required. Day of month. Must be from 1 to 31 and valid for the year and month.

• int32 hours = 4

  Required. Hours of day in 24 hour format. Should be from 0 to 23. An API may choose to allow the value "24:00:00" for scenarios like business closing time.

• int32 minutes = 5

  Required. Minutes of hour of day. Must be from 0 to 59.

• int32 seconds = 6

  Required. Seconds of minutes of the time. Must normally be from 0 to 59. An API may allow the value 60 if it allows leap-seconds.

• int32 nanos = 7

  Required. Fractions of seconds in nanoseconds. Must be from 0 to 999,999,999.

• oneof time_offset

  Optional. Specifies either the UTC offset or the time zone of the DateTime. Choose carefully between them, considering that time zone data may change in the future (for example, a country modifies their DST start/end dates, and future DateTimes in the affected range had already been stored). If omitted, the DateTime is considered to be in local time.

  • protobuf.Duration utc_offset = 8

    UTC offset. Must be whole seconds, between -18 hours and +18 hours. For example, a UTC offset of -4:00 would be represented as { seconds: -14400 }.

  • TimeZone time_zone = 9

    Time zone.

Represents an amount of money with its currency type.

Used in: payment.Order

• string currency_code = 1

  The three-letter currency code defined in ISO 4217.

• int64 units = 2

  The whole units of the amount. For example if `currencyCode` is `"USD"`, then 1 unit is one US dollar.

• int32 nanos = 3

  Number of nano (10^-9) units of the amount. The value must be between -999,999,999 and +999,999,999 inclusive. If `units` is positive, `nanos` must be positive or zero. If `units` is zero, `nanos` can be positive, zero, or negative. If `units` is negative, `nanos` must be negative or zero. For example $-1.75 is represented as `units`=-1 and `nanos`=-750,000,000.

Represents a time zone from the [IANA Time Zone Database](https://www.iana.org/time-zones).

Used in: DateTime

• string id = 1

  IANA Time Zone Database time zone, e.g. "America/New_York".

• string version = 2

  Optional. IANA Time Zone Database version number, e.g. "2019a".