Default scope overriding

[adousa]

Feature Request: Ability to Override Default Google Picker Scope

Description:

I would like to request a new feature that allows developers to override the default scope used to connect to Google Picker. Currently, the library uses a predefined scope

https://www.googleapis.com/auth/drive.readonly

which gives access to see and download all Google Drive files for a user

Use Case:

In many applications, accessing files selected by user in the picker is only required by using:

https://www.googleapis.com/auth/drive.file

[sterliakov]

You can extend the default scope, but unfortunately not override, so drive.file is just lost (as it's weaker than drive.readonly). I think this can be either changed extremely (never concatenate, use the scopes provided in config if any) with a major version bump or less destructively (add a second option - includeDefaultScope = true). I am ready to contribute either, @Jose-cd may I ask for your opinion on this?

[sterliakov]

To clarify, this difference is critical because drive.file is a "free" scope that does not require app validation from Google, while drive.readonly is sensitive and requires such audit. This is a deal-breaker for anybody with a burning deadline.

[johnsonfamily1234]

Is there any movement on this? I'm hitting the drive.file limitation - even when passing an appId it doesn't seem to be working properly. We don't have drive.readonly in our project (google verification process strongly discouraged it) and this is currently a pretty heavy issue for us.