google-cloud-channel-v1 2.4.1 → 2.5.0

data/proto_docs/google/type/decimal.rb

@@ -20,12 +20,10 @@
 module Google
   module Type
     # 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
-    # [decimal.Decimal]: https://docs.python.org/3/library/decimal.html
+    # into language-native decimal formats, such as Java's
+    # [BigDecimal](https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/math/BigDecimal.html)
+    # or Python's
+    # [decimal.Decimal](https://docs.python.org/3/library/decimal.html).
     # @!attribute [rw] value
     #   @return [::String]
     #     The decimal value, as a string.
@@ -33,7 +31,7 @@ module Google
     #     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.
+    #     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
@@ -47,12 +45,13 @@ module Google
     #
     #       - 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`).
+    #       - 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`).
+    #     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.
     #
@@ -64,7 +63,7 @@ module Google
     #     The ENBF grammar is:
     #
     #         DecimalString =
-    #           [Sign] Significand [Exponent];
+    #           '' | [Sign] Significand [Exponent];
     #
     #         Sign = '+' | '-';
     #

data/proto_docs/google/type/postal_address.rb

@@ -19,23 +19,23 @@
 
 module Google
   module Type
-    # Represents a postal address, e.g. for postal delivery or payments addresses.
-    # Given a postal address, a postal service can deliver items to a premise, P.O.
-    # Box or similar.
-    # It is not intended to model geographical locations (roads, towns,
-    # mountains).
+    # Represents a postal address, such as for postal delivery or payments
+    # addresses. With a postal address, a postal service can deliver items to a
+    # premise, P.O. box, or similar. A postal address is not intended to model
+    # geographical locations like roads, towns, or mountains.
     #
-    # In typical usage an address would be created via user input or from importing
+    # In typical usage, an address would be created by user input or from importing
     # existing data, depending on the type of process.
     #
-    # Advice on address input / editing:
-    #  - Use an i18n-ready address widget such as
-    #    https://github.com/google/libaddressinput)
-    # - Users should not be presented with UI elements for input or editing of
-    #   fields outside countries where that field is used.
+    # Advice on address input or editing:
     #
-    # For more guidance on how to use this schema, please see:
-    # https://support.google.com/business/answer/6397478
+    #  - Use an internationalization-ready address widget such as
+    #  https://github.com/google/libaddressinput.
+    #  - Users should not be presented with UI elements for input or editing of
+    #  fields outside countries where that field is used.
+    #
+    # For more guidance on how to use this schema, see:
+    # https://support.google.com/business/answer/6397478.
     # @!attribute [rw] revision
     #   @return [::Integer]
     #     The schema revision of the `PostalAddress`. This must be set to 0, which is
@@ -46,8 +46,8 @@ module Google
     #   @return [::String]
     #     Required. CLDR region code of the country/region of the address. This
     #     is never inferred and it is up to the user to ensure the value is
-    #     correct. See http://cldr.unicode.org/ and
-    #     http://www.unicode.org/cldr/charts/30/supplemental/territory_information.html
+    #     correct. See https://cldr.unicode.org/ and
+    #     https://www.unicode.org/cldr/charts/30/supplemental/territory_information.html
     #     for details. Example: "CH" for Switzerland.
     # @!attribute [rw] language_code
     #   @return [::String]
@@ -67,55 +67,56 @@ module Google
     #   @return [::String]
     #     Optional. Postal code of the address. Not all countries use or require
     #     postal codes to be present, but where they are used, they may trigger
-    #     additional validation with other parts of the address (e.g. state/zip
-    #     validation in the U.S.A.).
+    #     additional validation with other parts of the address (for example,
+    #     state or zip code validation in the United States).
     # @!attribute [rw] sorting_code
     #   @return [::String]
     #     Optional. Additional, country-specific, sorting code. This is not used
     #     in most regions. Where it is used, the value is either a string like
-    #     "CEDEX", optionally followed by a number (e.g. "CEDEX 7"), or just a number
-    #     alone, representing the "sector code" (Jamaica), "delivery area indicator"
-    #     (Malawi) or "post office indicator" (e.g. Côte d'Ivoire).
+    #     "CEDEX", optionally followed by a number (for example, "CEDEX 7"), or just
+    #     a number alone, representing the "sector code" (Jamaica), "delivery area
+    #     indicator" (Malawi) or "post office indicator" (Côte d'Ivoire).
     # @!attribute [rw] administrative_area
     #   @return [::String]
     #     Optional. Highest administrative subdivision which is used for postal
     #     addresses of a country or region.
     #     For example, this can be a state, a province, an oblast, or a prefecture.
-    #     Specifically, for Spain this is the province and not the autonomous
-    #     community (e.g. "Barcelona" and not "Catalonia").
-    #     Many countries don't use an administrative area in postal addresses. E.g.
-    #     in Switzerland this should be left unpopulated.
+    #     For Spain, this is the province and not the autonomous
+    #     community (for example, "Barcelona" and not "Catalonia").
+    #     Many countries don't use an administrative area in postal addresses. For
+    #     example, in Switzerland, this should be left unpopulated.
     # @!attribute [rw] locality
     #   @return [::String]
-    #     Optional. Generally refers to the city/town portion of the address.
+    #     Optional. Generally refers to the city or town portion of the address.
     #     Examples: US city, IT comune, UK post town.
     #     In regions of the world where localities are not well defined or do not fit
-    #     into this structure well, leave locality empty and use address_lines.
+    #     into this structure well, leave `locality` empty and use `address_lines`.
     # @!attribute [rw] sublocality
     #   @return [::String]
     #     Optional. Sublocality of the address.
-    #     For example, this can be neighborhoods, boroughs, districts.
+    #     For example, this can be a neighborhood, borough, or district.
     # @!attribute [rw] address_lines
     #   @return [::Array<::String>]
     #     Unstructured address lines describing the lower levels of an address.
     #
-    #     Because values in address_lines do not have type information and may
-    #     sometimes contain multiple values in a single field (e.g.
+    #     Because values in `address_lines` do not have type information and may
+    #     sometimes contain multiple values in a single field (for example,
     #     "Austin, TX"), it is important that the line order is clear. The order of
-    #     address lines should be "envelope order" for the country/region of the
-    #     address. In places where this can vary (e.g. Japan), address_language is
-    #     used to make it explicit (e.g. "ja" for large-to-small ordering and
-    #     "ja-Latn" or "en" for small-to-large). This way, the most specific line of
-    #     an address can be selected based on the language.
+    #     address lines should be "envelope order" for the country or region of the
+    #     address. In places where this can vary (for example, Japan),
+    #     `address_language` is used to make it explicit (for example, "ja" for
+    #     large-to-small ordering and "ja-Latn" or "en" for small-to-large). In this
+    #     way, the most specific line of an address can be selected based on the
+    #     language.
     #
     #     The minimum permitted structural representation of an address consists
-    #     of a region_code with all remaining information placed in the
-    #     address_lines. It would be possible to format such an address very
+    #     of a `region_code` with all remaining information placed in the
+    #     `address_lines`. It would be possible to format such an address very
     #     approximately without geocoding, but no semantic reasoning could be
     #     made about any of the address components until it was at least
     #     partially resolved.
     #
-    #     Creating an address only containing a region_code and address_lines, and
+    #     Creating an address only containing a `region_code` and `address_lines` and
     #     then geocoding is the recommended way to handle completely unstructured
     #     addresses (as opposed to guessing which parts of the address should be
     #     localities or administrative areas).

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: google-cloud-channel-v1
 version: !ruby/object:Gem::Version
-  version: 2.4.1
+  version: 2.5.0
 platform: ruby
 authors:
 - Google LLC
@@ -130,7 +130,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: '3.1'
+      version: '3.2'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="