Several APIs: Some properties are missing a type
@jonesfloyd ya está trabajando en esto.
Desde el 26/1/2023.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
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?
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 118
- Forks
- 94
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de googlemaps/openapi-specification
-
triage me type: feature request
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
googlemaps/openapi-specification#521 · 1 reacción ·
-
triage me type: feature request
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
googlemaps/openapi-specification#485 · 4 comentarios · 5 reacciones ·
-
triage me type: bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 55/100
googlemaps/openapi-specification#484 · 1 comentario ·
-
triage me type: bug
Dificultad 3/5 1-2 días Aptitud para principiantes 30/100
googlemaps/openapi-specification#483 · 1 comentario ·
-
[Place Details API response] geometry field - LatLngLiteral does not specify the geocode levelAbiertotriage me type: bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 38/100
googlemaps/openapi-specification#464 · 1 comentario ·