-
Notifications
You must be signed in to change notification settings - Fork 386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add More OAuth Providers #245
Conversation
Uppon reading that further it looks like it may be ok. I haven't been able to test this fully as my gotrue environment locally isn't perfect. Maybe @kangmingtay could test this at some point? Also before merge would this need some sort of tests added? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I fixed a few things, will add a few tests tonight if I get round to it 👍
looks good thanks for implementing @HarryET
@awalias Thanks! Was my first "big" PR to sup abase so any feedback would be cool. If you want I could try add tests? |
@HarryET main feedback would be in future to break them out into separate PRs, that way if slack is buggy, we can still merge spotify etc. but no worries for this one 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@HarryET would you be able to try adding some tests in a follow up PR? You can probably use the other external tests as a base
I will merge this one so I can test it out in our stack, but it's working for me locally end-to-end
🎉 This PR is included in version 2.1.17 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Added in GoTrue PR - supabase/auth#245
* Slack * Spotify supabase/auth#245
* Slack * Spotify supabase/auth#245
Added in GoTrue PR - supabase/auth#245
Add More OAuth Providers
What kind of change does this PR introduce?
This adds new requested OAuth providers:
What is the current behavior?
No support for new OAuth Providers
What is the new behavior?
Support for new OAuth Providers
Additional context
https://twitter.com/supabase/status/1451316743859752963