-
-
Notifications
You must be signed in to change notification settings - Fork 855
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
New places api #943
New places api #943
Conversation
Awaiting your confirmation to proceed with the merge |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two more changes are required to make this work with the new BE changes to support locationBias
@FaridSafi @rafecolton The PR here is ready for review as it works well with the new places API. |
Thank you @rojiphil, merged and deployed. Could you please double check if the published version is OK ? |
|
||
request.withCredentials = requestShouldUseWithCredentials(); | ||
setRequestHeaders(request, getRequestHeaders(props.requestUrl)); | ||
|
||
request.send(); | ||
if (props.isNewPlacesAPI) { | ||
const { key, locationbias, types, ...rest } = props.query; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it necessary to maintain locaitonbias
in here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
locationbias
is for old Places API and can be stripped whereas locationBias
is what is expected in new Places API. We maintain locationBias
for new Places API.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah got it, thank you for explaining 👍
Thanks @FaridSafi! I see the version published on NPM |
@FaridSafi Coming from this issue, this PR attempt to support
Autocomplete (New)
andPlace Details (New)
API. Also, this PR addssessionToken
support.