@maxim_mazurok/gapi.client.places-v1 0.0.20250316 → 0.0.20250319

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 +11 -11
  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://places.googleapis.com/$discovery/rest?version=v1
12
- // Revision: 20250316
12
+ // Revision: 20250319
13
13
 
14
14
  /// <reference types="gapi.client" />
15
15
 
@@ -351,7 +351,7 @@ declare namespace gapi.client {
351
351
  pureServiceAreaBusiness?: boolean;
352
352
  /** A rating between 1.0 and 5.0, based on user reviews of this place. */
353
353
  rating?: number;
354
- /** The regular hours of operation. Note that if a place is always open (24 hours), the `close` field will not be set. Clients can rely on always open (24 hours) being represented as an `open` period containing `day` with value `0`, `hour` with value `0`, and `minute` with value `0`. */
354
+ /** The regular hours of operation. Note that if a place is always open (24 hours), the `close` field will not be set. Clients can rely on always open (24 hours) being represented as an [`open`](https://developers.google.com/maps/documentation/places/web-service/reference/rest/v1/places#Period) period containing [`day`](https://developers.google.com/maps/documentation/places/web-service/reference/rest/v1/places#Point) with value `0`, [`hour`](https://developers.google.com/maps/documentation/places/web-service/reference/rest/v1/places#Point) with value `0`, and [`minute`](https://developers.google.com/maps/documentation/places/web-service/reference/rest/v1/places#Point) with value `0`. */
355
355
  regularOpeningHours?: GoogleMapsPlacesV1PlaceOpeningHours;
356
356
  /** Contains an array of entries for information about regular secondary hours of a business. Secondary hours are different from a business's main hours. For example, a restaurant can specify drive through hours or delivery hours as its secondary hours. This field populates the type subfield, which draws from a predefined list of opening hours types (such as DRIVE_THROUGH, PICKUP, or TAKEOUT) based on the types of the place. */
357
357
  regularSecondaryOpeningHours?: GoogleMapsPlacesV1PlaceOpeningHours[];
@@ -383,7 +383,7 @@ declare namespace gapi.client {
383
383
  servesWine?: boolean;
384
384
  /** A short, human-readable address for this place. */
385
385
  shortFormattedAddress?: string;
386
- /** A list of sub destinations related to the place. */
386
+ /** A list of sub-destinations related to the place. */
387
387
  subDestinations?: GoogleMapsPlacesV1PlaceSubDestination[];
388
388
  /** Specifies if the business supports takeout. */
389
389
  takeout?: boolean;
@@ -533,9 +533,9 @@ declare namespace gapi.client {
533
533
  globalCode?: string;
534
534
  }
535
535
  interface GoogleMapsPlacesV1PlaceSubDestination {
536
- /** The place id of the sub destination. */
536
+ /** The place id of the sub-destination. */
537
537
  id?: string;
538
- /** The resource name of the sub destination. */
538
+ /** The resource name of the sub-destination. */
539
539
  name?: string;
540
540
  }
541
541
  interface GoogleMapsPlacesV1Polyline {
@@ -737,17 +737,17 @@ declare namespace gapi.client {
737
737
  units?: string;
738
738
  }
739
739
  interface GoogleTypePostalAddress {
740
- /** 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 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). */
740
+ /** 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 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). */
741
741
  addressLines?: string[];
742
- /** 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. */
742
+ /** 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. 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. */
743
743
  administrativeArea?: string;
744
744
  /** Optional. BCP-47 language code of the contents of this address (if known). This is often the UI language of the input form or is expected to match one of the languages used in the address' country/region, or their transliterated equivalents. This can affect formatting in certain countries, but is not critical to the correctness of the data and will never affect any validation or other non-formatting related operations. If this value is not known, it should be omitted (rather than specifying a possibly incorrect default). Examples: "zh-Hant", "ja", "ja-Latn", "en". */
745
745
  languageCode?: string;
746
- /** 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. */
746
+ /** 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`. */
747
747
  locality?: string;
748
748
  /** Optional. The name of the organization at the address. */
749
749
  organization?: string;
750
- /** 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.). */
750
+ /** 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 or zip code validation in the United States). */
751
751
  postalCode?: string;
752
752
  /** Optional. The recipient at the address. This field may, under certain circumstances, contain multiline information. For example, it might contain "care of" information. */
753
753
  recipients?: string[];
@@ -755,9 +755,9 @@ declare namespace gapi.client {
755
755
  regionCode?: string;
756
756
  /** The schema revision of the `PostalAddress`. This must be set to 0, which is the latest revision. All new revisions **must** be backward compatible with old revisions. */
757
757
  revision?: number;
758
- /** 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 alone, representing the "sector code" (Jamaica), "delivery area indicator" (Malawi) or "post office indicator" (For example Côte d'Ivoire). */
758
+ /** 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 alone, representing the "sector code" (Jamaica), "delivery area indicator" (Malawi) or "post office indicator" (Côte d'Ivoire). */
759
759
  sortingCode?: string;
760
- /** Optional. Sublocality of the address. For example, this can be neighborhoods, boroughs, districts. */
760
+ /** Optional. Sublocality of the address. For example, this can be a neighborhood, borough, or district. */
761
761
  sublocality?: string;
762
762
  }
763
763
  interface GoogleTypeTimeZone {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@maxim_mazurok/gapi.client.places-v1",
3
- "version": "0.0.20250316",
3
+ "version": "0.0.20250319",
4
4
  "description": "TypeScript typings for Places API (New) v1",
5
5
  "repository": {
6
6
  "type": "git",