Closed ndnam198 closed 3 weeks ago
I thought this update was a bug that was introduced by Google and later was removed. Do you have any thing that says the change was intentional and is here for good?
Thanks for reply.
yes, you are right. Previously I have to add these minimum scope values into library code just to pass throught Google authentication in my own project (which also uses this package). As a result, I realize that this package has not used the passed in scopes
anywhere. That's why I think it can be good to leverage the variable somehow.
But yes, since Google fixed the issue, minimum could be empty array rather than certain values.
So I think you can reject the PR for now and maybe apply the changes in the future when there are actual needs.
What kind of change does this PR introduce?
What is the current behavior?
What is the new behavior?