Switch to using provider-specific classes, when available #23
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It turns out that the
OAuth2class does not work when the provider has an Arcade well-known configuration and the user creates a custom OAuth provider. In order to work with well-known providers and custom OAuth providers, we must use the provider-specific class (e.g.auth.Slack), instead ofOAuth2(id="arcade-slack").This PR updates the current starter tools with an OAuth provider that has a specific class in Arcade's
authmodule. The remaining tools that have OAuth requirement but no specific class available, we changed theidfromarcade-{provider}to just{provider}.