Repository navigation
Reason for requiring the old places api permission? #447
|
Hey all, I'm using the package for autocomplete, and was getting permissions errors until I added the old What does the package use the old places API for? Thanks |
Answered by
usefulthink
Jul 12, 2024
Replies: 1 comment
|
It seems that Google is in the middle of a migration from an older API architecture to a newer one, which requires the new scope to be added for some features. They probably don't want to (or haven't yet completed) port all the functionality of the old services over to the new one, so for now there are two of them. That's just how it is, and it has nothing to do with our library. (Note: I'm not a googler and don't have insights into their development, this is all just observations and educated guessing) |
0 replies
Answer selected by
usefulthink
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems that Google is in the middle of a migration from an older API architecture to a newer one, which requires the new scope to be added for some features. They probably don't want to (or haven't yet completed) port all the functionality of the old services over to the new one, so for now there are two of them.
That's just how it is, and it has nothing to do with our library.
(Note: I'm not a googler and don't have insights into their development, this is all just observations and educated guessing)