google-apis-addressvalidation_v1 0.5.0 → 0.7.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 0a1ffe764574a77e623ed9b42aa0b1a2ef7ea710d2c30ac613d1355683474f3e
-  data.tar.gz: 0f78ffd8047c95350942136f6ab8889de93013d4a375616fd62d9c9b7a92eacb
+  metadata.gz: a80d3da9e95ed70e0f84745cd8e81c9ec0b562c7135858b063f6842d37993844
+  data.tar.gz: 43474e09a845da6d796cdfddb434aca067bb9458de5cdeb77564ba8567c572a7
 SHA512:
-  metadata.gz: c76961db5de16744bd96773467e895c31166b404cbc8828ffc9bb1c89ce4a5ae9c78612cf862f4a4963200e6776480dc661f24b7cb8c61754473f85a877f7979
-  data.tar.gz: 32e2269ccf8eb55d075e9c49fa11dec894c35a3c84b079c52019a31c6c152b2fedc6c277a16274afaecc9d42648eea7ae7349236713de80eddc5d60bd215f211
+  metadata.gz: 8d7776e0d9343b10e24e36da65efaa243f01833b334cff895e50a2f181a0a88336a3c27be3cf2f1090817f2befdc81e9807ac9def8efebec14e0092eaba35087
+  data.tar.gz: df25a7ba465c60faa1880127a07cef14d1c28204e57f08a4901ab497e3b120468abd0aba0b6277480aa6fd3eaf8167ecad84c3a0e9292f5e921d418558db1892

data/CHANGELOG.md

@@ -1,5 +1,14 @@
 # Release history for google-apis-addressvalidation_v1
 
+### v0.7.0 (2025-03-30)
+
+* Regenerated from discovery document revision 20250323
+
+### v0.6.0 (2025-03-23)
+
+* Regenerated from discovery document revision 20250318
+* Regenerated using generator version 0.16.0
+
 ### v0.5.0 (2024-11-24)
 
 * Regenerated from discovery document revision 20241120

data/lib/google/apis/addressvalidation_v1/classes.rb

@@ -95,25 +95,29 @@ module Google
       
         # The types of components that were expected to be present in a correctly
         # formatted mailing address but were not found in the input AND could not be
-        # inferred. Components of this type are not present in `formatted_address`, `
-        # postal_address`, or `address_components`. An example might be `['street_number'
-        # , 'route']` for an input like "Boulder, Colorado, 80301, USA". The list of
-        # possible types can be found [here](https://developers.google.com/maps/
-        # documentation/geocoding/requests-geocoding#Types).
+        # inferred. An example might be `['street_number', 'route']` for an input like "
+        # Boulder, Colorado, 80301, USA". The list of possible types can be found [here](
+        # https://developers.google.com/maps/documentation/geocoding/requests-geocoding#
+        # Types). **Note: you might see a missing component type when you think you've
+        # already supplied the missing component.** For example, this can happen when
+        # the input address contains the building name, but not the premise number. In
+        # the address "渋谷区渋谷３丁目　Shibuya Stream", the building name "Shibuya Stream" has
+        # the component type `premise`, but the premise number is missing, so `
+        # missing_component_types` will contain `premise`.
         # Corresponds to the JSON property `missingComponentTypes`
         # @return [Array<String>]
         attr_accessor :missing_component_types
       
-        # Represents a postal address. For example 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). In typical usage an address would be
+        # Represents a postal address (for example, 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). 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 internationalization-
-        # ready address widget such as https://github.com/google/libaddressinput) -
+        # of process. Advice on address input or editing: - 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
+        # this schema, see: https://support.google.com/business/answer/6397478.
         # Corresponds to the JSON property `postalAddress`
         # @return [Google::Apis::AddressvalidationV1::GoogleTypePostalAddress]
         attr_accessor :postal_address
@@ -858,16 +862,16 @@ module Google
       class GoogleMapsAddressvalidationV1ValidateAddressRequest
         include Google::Apis::Core::Hashable
       
-        # Represents a postal address. For example 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). In typical usage an address would be
+        # Represents a postal address (for example, 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). 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 internationalization-
-        # ready address widget such as https://github.com/google/libaddressinput) -
+        # of process. Advice on address input or editing: - 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
+        # this schema, see: https://support.google.com/business/answer/6397478.
         # Corresponds to the JSON property `address`
         # @return [Google::Apis::AddressvalidationV1::GoogleTypePostalAddress]
         attr_accessor :address
@@ -1132,46 +1136,46 @@ module Google
         end
       end
       
-      # Represents a postal address. For example 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). In typical usage an address would be
+      # Represents a postal address (for example, 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). 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 internationalization-
-      # ready address widget such as https://github.com/google/libaddressinput) -
+      # of process. Advice on address input or editing: - 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
+      # this schema, see: https://support.google.com/business/answer/6397478.
       class GoogleTypePostalAddress
         include Google::Apis::Core::Hashable
       
         # 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 (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 (
-        # 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).
-        # 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
+        # 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 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
         # 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 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).
+        # 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).
         # Corresponds to the JSON property `addressLines`
         # @return [Array<String>]
         attr_accessor :address_lines
       
         # 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 (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.
+        # an oblast, or a prefecture. 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.
         # Corresponds to the JSON property `administrativeArea`
         # @return [String]
         attr_accessor :administrative_area
@@ -1188,10 +1192,10 @@ module Google
         # @return [String]
         attr_accessor :language_code
       
-        # Optional. Generally refers to the city/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.
+        # 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`.
         # Corresponds to the JSON property `locality`
         # @return [String]
         attr_accessor :locality
@@ -1203,8 +1207,8 @@ module Google
       
         # 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 (For example state/zip validation
-        # in the U.S.A.).
+        # validation with other parts of the address (for example, state or zip code
+        # validation in the United States).
         # Corresponds to the JSON property `postalCode`
         # @return [String]
         attr_accessor :postal_code
@@ -1233,15 +1237,15 @@ module Google
       
         # 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 (For example "CEDEX 7"), or just a number
+        # 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" (For example Côte d'Ivoire).
+        # Malawi) or "post office indicator" (Côte d'Ivoire).
         # Corresponds to the JSON property `sortingCode`
         # @return [String]
         attr_accessor :sorting_code
       
-        # Optional. Sublocality of the address. For example, this can be neighborhoods,
-        # boroughs, districts.
+        # Optional. Sublocality of the address. For example, this can be a neighborhood,
+        # borough, or district.
         # Corresponds to the JSON property `sublocality`
         # @return [String]
         attr_accessor :sublocality

data/lib/google/apis/addressvalidation_v1/gem_version.rb

@@ -16,13 +16,13 @@ module Google
   module Apis
     module AddressvalidationV1
       # Version of the google-apis-addressvalidation_v1 gem
-      GEM_VERSION = "0.5.0"
+      GEM_VERSION = "0.7.0"
 
       # Version of the code generator used to generate this client
-      GENERATOR_VERSION = "0.15.1"
+      GENERATOR_VERSION = "0.16.0"
 
       # Revision of the discovery document this client was generated from
-      REVISION = "20241120"
+      REVISION = "20250323"
     end
   end
 end

metadata

@@ -1,14 +1,13 @@
 --- !ruby/object:Gem::Specification
 name: google-apis-addressvalidation_v1
 version: !ruby/object:Gem::Version
-  version: 0.5.0
+  version: 0.7.0
 platform: ruby
 authors:
 - Google LLC
-autorequire: 
 bindir: bin
 cert_chain: []
-date: 2024-12-04 00:00:00.000000000 Z
+date: 2025-03-30 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: google-apis-core
@@ -58,9 +57,8 @@ licenses:
 metadata:
   bug_tracker_uri: https://github.com/googleapis/google-api-ruby-client/issues
   changelog_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-addressvalidation_v1/CHANGELOG.md
-  documentation_uri: https://googleapis.dev/ruby/google-apis-addressvalidation_v1/v0.5.0
+  documentation_uri: https://googleapis.dev/ruby/google-apis-addressvalidation_v1/v0.7.0
   source_code_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-addressvalidation_v1
-post_install_message: 
 rdoc_options: []
 require_paths:
 - lib
@@ -75,8 +73,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.5.22
-signing_key: 
+rubygems_version: 3.6.5
 specification_version: 4
 summary: Simple REST client for Address Validation API V1
 test_files: []