googlemaps / googlemaps/openapi-specification

Roads: snapToRoads has incorrect URL in spec

Open
#484 1 comment 0 reactions 0 assignees View on GitHub
triage me type: bug
Dominant language
No language data
Stars
119
Forks
95
PR merge metrics
No merged PRs in 30d

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!

Contributor guide

Open the contributing guide

Research direction

Search the YAML and JSON schemas for the snapToRoads operation and inspect its encoded URL. Correct the path casing from /v1/snaptoroads to /v1/snapToRoads in the affected schema files, then verify that both schemas contain the corrected path and that the lowercase URL is no longer present.

Written by the indexing model from the issue text.

Assessment

Tech stack
openapi
Domain
api
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.