Closed BytewaveMLP closed 1 year ago
Thanks for this. I'm open to a pull request to fix it. Looks like an easy change, just two lines.
I can open a PR tomorrow, just wanted to confirm that was an acceptable solution as it would change the default result set without a suitable replacement.
Good to take that into consideration. But we have to change it if the default is an error. Let's just get rid of those two "legacy" fields, right?
Sure, sounds good.
When attempting to perform a Places Search API lookup for a given location using the default fields specified by the gem, no results are returned, and an error is printed to the console due to the use of deprecated and now removed
id
andreference
fields.Expected behavior
The default fieldset specified by the gem should be valid.
Actual behavior
The following error is printed and no results are returned:
Steps to reproduce
search
request withlookup: :google_places_search
without specifyingfield:
Environment info
google_places_search