@maxim_mazurok/gapi.client.addressvalidation-v1 0.0.20250610 → 0.0.20250615

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/index.d.ts +8 -4
  2. package/package.json +1 -1
package/index.d.ts CHANGED
@@ -9,7 +9,7 @@
9
9
  // This file was generated by https://github.com/Maxim-Mazurok/google-api-typings-generator. Please do not edit it manually.
10
10
  // In case of any problems please post issue to https://github.com/Maxim-Mazurok/google-api-typings-generator
11
11
  // Generated from: https://addressvalidation.googleapis.com/$discovery/rest?version=v1
12
- // Revision: 20250610
12
+ // Revision: 20250615
13
13
 
14
14
  /// <reference types="gapi.client" />
15
15
 
@@ -238,7 +238,7 @@ declare namespace gapi.client {
238
238
  verdict?: GoogleMapsAddressvalidationV1Verdict;
239
239
  }
240
240
  interface GoogleMapsAddressvalidationV1Verdict {
241
- /** The address is considered complete if there are no unresolved tokens, no unexpected or missing address components. If unset, indicates that the value is `false`. See `missing_component_types`, `unresolved_tokens` or `unexpected` fields for more details. */
241
+ /** The post-processed address is considered complete if there are no unresolved tokens, no unexpected or missing address components. If unset, indicates that the value is `false`. See `missing_component_types`, `unresolved_tokens` or `unexpected` fields for more details. */
242
242
  addressComplete?: boolean;
243
243
  /** Information about the granularity of the `geocode`. This can be understood as the semantic meaning of how coarse or fine the geocoded location is. This can differ from the `validation_granularity` above occasionally. For example, our database might record the existence of an apartment number but do not have a precise location for the apartment within a big apartment complex. In that case, the `validation_granularity` will be `SUB_PREMISE` but the `geocode_granularity` will be `PREMISE`. */
244
244
  geocodeGranularity?: string;
@@ -246,11 +246,15 @@ declare namespace gapi.client {
246
246
  hasInferredComponents?: boolean;
247
247
  /** At least one address component was replaced, see [google.maps.addressvalidation.v1.Address.address_components] for details. */
248
248
  hasReplacedComponents?: boolean;
249
+ /** At least one address component was spell-corrected, see [google.maps.addressvalidation.v1.Address.address_components] for details. */
250
+ hasSpellCorrectedComponents?: boolean;
249
251
  /** At least one address component cannot be categorized or validated, see [google.maps.addressvalidation.v1.Address.address_components] for details. */
250
252
  hasUnconfirmedComponents?: boolean;
251
- /** The granularity of the **input** address. This is the result of parsing the input address and does not give any validation signals. For validation signals, refer to `validation_granularity` below. For example, if the input address includes a specific apartment number, then the `input_granularity` here will be `SUB_PREMISE`. If we cannot match the apartment number in the databases or the apartment number is invalid, the `validation_granularity` will likely be `PREMISE` or worse. */
253
+ /** The granularity of the **input** address. This is the result of parsing the input address and does not give any validation signals. For validation signals, refer to `validation_granularity` below. For example, if the input address includes a specific apartment number, then the `input_granularity` here will be `SUB_PREMISE`. If we cannot match the apartment number in the databases or the apartment number is invalid, the `validation_granularity` will likely be `PREMISE` or more coarse. */
252
254
  inputGranularity?: string;
253
- /** The granularity level that the API can fully **validate** the address to. For example, an `validation_granularity` of `PREMISE` indicates all address components at the level of `PREMISE` or more coarse can be validated. Per address component validation result can be found in [google.maps.addressvalidation.v1.Address.address_components]. */
255
+ /** Preview: This feature is in Preview (pre-GA). Pre-GA products and features might have limited support, and changes to pre-GA products and features might not be compatible with other pre-GA versions. Pre-GA Offerings are covered by the [Google Maps Platform Service Specific Terms](https://cloud.google.com/maps-platform/terms/maps-service-terms). For more information, see the [launch stage descriptions](https://developers.google.com/maps/launch-stages). Offers an interpretive summary of the API response, intended to assist in determining a potential subsequent action to take. This field is derived from other fields in the API response and should not be considered as a guarantee of address accuracy or deliverability. See [Build your validation logic](https://developers.google.com/maps/documentation/address-validation/build-validation-logic) for more details. */
256
+ possibleNextAction?: string;
257
+ /** The level of granularity for the post-processed address that the API can fully validate. For example, a `validation_granularity` of `PREMISE` indicates all address components at the level of `PREMISE` or more coarse can be validated. Per address component validation result can be found in [google.maps.addressvalidation.v1.Address.address_components]. */
254
258
  validationGranularity?: string;
255
259
  }
256
260
  interface GoogleTypeLatLng {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@maxim_mazurok/gapi.client.addressvalidation-v1",
3
- "version": "0.0.20250610",
3
+ "version": "0.0.20250615",
4
4
  "description": "TypeScript typings for Address Validation API v1",
5
5
  "repository": {
6
6
  "type": "git",