Conversation
|
Thank you for this pull request!!!!! Setting the App ID is so important if you want to use drive.file scope. And drive.file scope is the BEST most minimal scope! After many hours of frustration this branch saved my project. Could this pull request please be merged? I would be happy to write some documentation on this. As it stands this node package will use drive.readonly scope by default. However if you have pre-obtained a token with only drive.file scope, then it will NOT ask for drive.readonly - which is excellent! |
Relies on branched version of google-drive-file-picker Jose-cd/React-google-drive-picker#30
src/typeDefs.ts
Outdated
| export type PickerConfiguration = { | ||
| clientId: string | ||
| developerKey: string | ||
| AppId?: string |
There was a problem hiding this comment.
Why AppId with a capital A letter?
There was a problem hiding this comment.
Looks like that must have been a typo. appId is already included on line 60, so I'll update the PR to remove this line.
3 participants
Although the app ID isn't always required, in some cases it is needed. For example, if using the drive.file scope, the picker won't work properly without the App ID. This pull request adds the option to specify the app ID.