At a quick glance, it appears that the Google Drive integration is currently using the Drive API v2, via the @purest/providers default 'google' config. If this is the case, Team Drive support (the ultimate aim of this ticket) unfortunately can't be enabled without first upgrading to Drive API v3.
I'm not familiar with purest, but it looks as though a custom config can easily be passed in to flip over to v3. Hopefully the changes required to migrate existing functionality to v3 would be reasonably small - and once on v3, supporting Team Drives looks to be relatively straightforward (I'm not sure how much of this affects uppy-server, or whether the Team Drive support would only affect uppy itself).
At a quick glance, it appears that the Google Drive integration is currently using the Drive API v2, via the
@purest/providersdefault 'google' config. If this is the case, Team Drive support (the ultimate aim of this ticket) unfortunately can't be enabled without first upgrading to Drive API v3.I'm not familiar with
purest, but it looks as though a custom config can easily be passed in to flip over to v3. Hopefully the changes required to migrate existing functionality to v3 would be reasonably small - and once on v3, supporting Team Drives looks to be relatively straightforward (I'm not sure how much of this affectsuppy-server, or whether the Team Drive support would only affectuppyitself).