You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While using the react-places-autocomplete library, I've encountered an issue related to the sessionToken prop in the searchOptions object.
Currently, the type definition for sessionToken is expecting an instance of google.maps.places.AutocompleteSessionToken, as per the error message: "InvalidValueError: in property sessionToken: not an instance of AutocompleteSessionToken". However, according to the Google Places API documentation, a session token should be a random string that identifies an autocomplete session for billing purposes. Google's recommendation is to use a version 4 UUID for this purpose.
In my application, I've followed Google's recommendation and generated a UUID string for sessionToken, but I'm encountering type errors due to the current type definition.
I suggest updating the type definition for sessionToken in the searchOptions prop to accept a string, in accordance with Google's guidelines. This would help users of the library to adhere to Google's recommendation for handling session tokens and avoid unnecessary type errors.
Thank you for your attention to this matter.
The text was updated successfully, but these errors were encountered:
Hello,
While using the react-places-autocomplete library, I've encountered an issue related to the sessionToken prop in the searchOptions object.
Currently, the type definition for sessionToken is expecting an instance of
google.maps.places.AutocompleteSessionToken
, as per the error message:"InvalidValueError: in property sessionToken: not an instance of AutocompleteSessionToken"
. However, according to the Google Places API documentation, a session token should be a random string that identifies an autocomplete session for billing purposes. Google's recommendation is to use a version 4 UUID for this purpose.In my application, I've followed Google's recommendation and generated a UUID string for sessionToken, but I'm encountering type errors due to the current type definition.
I suggest updating the type definition for sessionToken in the searchOptions prop to accept a string, in accordance with Google's guidelines. This would help users of the library to adhere to Google's recommendation for handling session tokens and avoid unnecessary type errors.
Thank you for your attention to this matter.
The text was updated successfully, but these errors were encountered: