googlemaps / googlemaps/openapi-specification
Roads: snapToRoads has incorrect URL in spec
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 119
- Forks
- 95
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
The url for snapToRoads is encoded as `/v1/snaptoroads` instead of `/v1/snapToRoads`.
---
**PLEASE READ**
If you have a support contract with Google, please create an issue in the [support console](https://cloud.google.com/support/). This will ensure a timely response.
Discover additional support services for the Google Maps Platform, including developer communities, technical guidance, and expert support at the Google Maps Platform [support resources page](https://developers.google.com/maps/support/).
If your bug or feature request is not related to this particular library, please visit the Google Maps Platform [issue trackers](https://developers.google.com/maps/support/#issue_tracker).
Check for answers on StackOverflow with the [google-maps](http://stackoverflow.com/questions/tagged/google-maps) tag.
---
Please be sure to include as much information as possible:
#### Environment details
1. Specify the API at the beginning of the title (for example, "Places: ...")
2. OS type and version
3. Library version and other environment information
#### Steps to reproduce
1. Open either the yml or json schema
2. Note that the url for snapToRoads is encoded as `/v1/snaptoroads` instead of `/v1/snapToRoads`
3. The lowercase version returns a 404.
#### Code example
```
# example
```
#### Stack trace
```
# example
```
Following these steps will guarantee the quickest resolution possible.
Thanks!
Guía de contribución
Línea de trabajo
Busca en los esquemas YAML y JSON la operación snapToRoads e inspecciona su URL codificada. Corrige las mayúsculas y minúsculas de la ruta de /v1/snaptoroads a /v1/snapToRoads en los archivos de esquema afectados y, después, verifica que ambos esquemas contengan la ruta corregida y que la URL en minúsculas ya no esté presente.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- openapi
- Área
- api
- Tipo de issue
- Error
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Estado de actividad
- Estancado
- Claridad
- Bien especificado
- Aptitud para principiantes
- 55/100