Version 0.5.4: findPlace "cannot read property 'split' of undefined"

[econner]

Hello,

I am getting the following error when trying to use findPlace with version 0.5.4 of this library:

TypeError: Cannot read property 'split' of undefined
    at /node_modules/@google/maps/lib/apis/places.js:58:37
    at /node_modules/@google/maps/lib/internal/validate.js:168:15
    at Array.forEach (native)
    at Object.validator (/node_modules/@google/maps/lib/internal/validate.js:167:16)
    at Object.findPlace (/node_modules/@google/maps/lib/index.js:55:25)

I am calling this method like so:

const results = await googleMapsClient.findPlace({
      input: query, 
      inputtype: 'textquery',
      fields: ['formatted_address','icon','photos','name','place_id'],
    })
    .asPromise()
    .then((response) => {
      return response.json.candidates
    })

I tracked it down and found that findPlace now expects a locationbias parameter that needs to be a string on line 58 of places.js (because split is called on it):

var parts = query.locationbias.split(':');

I was able to solve my problem by passing an empty string for locationbias:

const results = await googleMapsClient.findPlace({
      input: query, 
      inputtype: 'textquery',
      fields: ['formatted_address','icon','photos','name','place_id'],
      locationbias: ""
    })
    .asPromise()
    .then((response) => {
      return response.json.candidates
    })

But my guess is that locationbias should be optional rather than needing to pass an empty string.

[stephenmcd]

Thanks for the report - I just pushed a new version 0.5.5 with a fix.

[econner]

Thanks for the quick fix. I'll test it and follow up.