Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Places FindPlace Bug - Field "url" #456

Open
Portur opened this issue Apr 19, 2023 · 1 comment
Open

Places FindPlace Bug - Field "url" #456

Portur opened this issue Apr 19, 2023 · 1 comment
Assignees
Labels
triage me I really want to be triaged. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@Portur
Copy link

Portur commented Apr 19, 2023

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

Code example

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

Stack trace

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.

@Portur Portur added triage me I really want to be triaged. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Apr 19, 2023
@wangela
Copy link
Member

wangela commented Apr 19, 2023

If you would like to upvote the priority of this issue, please comment below or react with 👍 so we can see what is popular when we triage.

@Portur Thank you for opening this issue. 🙏
Please check out these other resources that might help you get to a resolution in the meantime:

This is an automated message, feel free to ignore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage me I really want to be triaged. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

No branches or pull requests

2 participants