googlemaps / googlemaps/openapi-specification

Places FindPlace Bug - Field "url"

Open
#456 1 comment 0 reactions 1 assignee Claimed by @wangela 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

#### Environment details

1. Place FindPlace - NodeJS Client
2. MacOS m1
3. "@googlemaps/google-maps-services-js": "3.3.28"

#### Steps to reproduce

1. Make a FindPlace call with fields `url` and `photo` as per documentation on https://developers.google.com/maps/documentation/places/web-service/search-find-place#Place

![image](https://user-images.githubusercontent.com/24350810/233030817-55b4dc39-a7a2-49a6-a0fd-28025e65ed60.png)

#### Code example

```javascript
const foundplace = await GoogleMapsClient.findPlaceFromText({
params: {
inputtype: 'textquery',
input: query.search_term,
key: GOOGLE_API_KEY,
fields: ['url'],
}
})
```

#### Stack trace
```json
data: {
candidates: [],
error_message: "Error while parsing 'fields' parameter: Unsupported field name 'url'. ",
status: 'INVALID_REQUEST'
}

```

Also as a side note. The documentation on that page says `photo` field is part of basic fields type. However the table to indicate all the available fields shows `photos` as plural. Using `photo` or `photos` still returns `photos` successfully.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.