Several APIs: Some properties are missing a type
@jonesfloyd y travaille déjà.
Depuis le 26/1/2023.
Évaluation
Cette issue n'a pas encore été évaluée.
Description
Sorry for deleting your nice template. If there isn't an obvious solution to this, I'll come back and fill out the full template. For now the file is just too big to parse out the exact details you require, and the issue is relatively simple and widespread.
Some properties are missing a type.
For example:
on line 23140:
steps:
description: Contains detailed directions for walking or driving steps in transit directions. Substeps are only available when travel_mode is set to "transit". The inner steps array is of the same type as steps.
And, on line 23288:
partial_match:
description: |
Indicates that the geocoder did not return an exact match for the original request, though it was able to match part of the requested address. You may wish to examine the original request for misspellings and/or an incomplete address.
Partial matches most often occur for street addresses that do not exist within the locality you pass in the request. Partial matches may also be returned when a request matches two or more locations in the same locality. For example, "21 Henr St, Bristol, UK" will return a partial match for both Henry Street and Henrietta Street. Note that if a request includes a misspelled address component, the geocoding service may suggest an alternative address. Suggestions triggered in this way will also be marked as a partial match.
This understandably trips up some code generators.
Is this expected behavior?
- Langage dominant
- Aucune donnée de langage
- Étoiles
- 118
- Forks
- 94
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Préparer son environnement
- Aucun Dockerfile ni fichier Docker Compose
- Aucun modèle de pull request
- Lire le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de googlemaps/openapi-specification
-
triage me type: feature request
Difficulté 5/5 Plus d'une semaine Accessibilité débutants 25/100
googlemaps/openapi-specification#521 · 1 réaction ·
-
triage me type: feature request
Difficulté 4/5 3-5 jours Accessibilité débutants 25/100
googlemaps/openapi-specification#485 · 4 commentaires · 5 réactions ·
-
triage me type: bug
Difficulté 2/5 1-3 heures Accessibilité débutants 55/100
googlemaps/openapi-specification#484 · 1 commentaire ·
-
triage me type: bug
Difficulté 3/5 1-2 jours Accessibilité débutants 30/100
googlemaps/openapi-specification#483 · 1 commentaire ·
-
[Place Details API response] geometry field - LatLngLiteral does not specify the geocode levelOuvertetriage me type: bug
Difficulté 2/5 1-3 heures Accessibilité débutants 38/100
googlemaps/openapi-specification#464 · 1 commentaire ·