googlemaps / googlemaps/openapi-specification
Roads: snapToRoads has incorrect URL in spec
- Langage dominant
- Aucune donnée de langage
- Étoiles
- 119
- Forks
- 95
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
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!
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Recherchez l’opération snapToRoads dans les schémas YAML et JSON et inspectez son URL encodée. Corrigez la casse du chemin, de /v1/snaptoroads à /v1/snapToRoads, dans les fichiers de schéma concernés, puis vérifiez que les deux schémas contiennent le chemin corrigé et que l’URL en minuscules n’est plus présente.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- openapi
- Domaine
- api
- Type d'issue
- Bug
- Difficulté
- 2/5
- Temps estimé
- 1-3 heures
- Activité
- À l'abandon
- Clarté
- Clairement spécifiée
- Accessibilité débutants
- 55/100