googleworkspace
Update quickstarts using default authentication
Has it been tested?
- [X] Development testing done
- [ ] Unit or integration test implemented
Checklist
- [X] My code follows the style guidelines of this project
- [X] I have performed a self-review of my own code
- [X] I have performed a peer-reviewed with team member(s)
- [X] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [X] My changes generate no new warnings
- [X] Any dependent changes have been merged and published in downstream modules
As with the other languages, holding this PR as it requires additional works in the docs + some usability testing before we can make this change
I'm not sure ADC is the right path here. Sure it's a simpler example, but my feeling is that most people wanting to interact with, for example the Gmail API, are writing user-facing applications, and showing how an oauth2 negotiation happens has a lot more value. That's just my perspective though.
It's a little tough -- OAuth 2.0 flows vary a lot by the application form factor (installed app vs. server-side web vs. client-side web vs. android vs. ios, etc..)
And while ADC isn't ideal, no option is ideal. It'll always be wrong for some % of developers. The point is more to decouple oauth from specific API examples while still expressing that some form oauth is required.
In any case, no plans to merge this right now :)