-
-
Notifications
You must be signed in to change notification settings - Fork 171
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
Enable passing scopes to provider #66
Conversation
Wow, nice @mateomorris @Beamanator 💯 Not sure what's going on with this test case. Perhaps some settings changed on GoTrue? I'll check with Ant, but otherwise this looks great |
Thanks @kiwicopple! Not sure what's going on there; I'll check too |
just needs 98b4a4f |
and docs are incoming: supabase/supabase#849 |
OK great everyone. This is an amazing PR - new functionality, updates to the server, updates to the client, updates to the docs ⚡ Thank you for all the help @mateomorris @Beamanator. I'll merge this now, once it's released I'll add it to supabase-js, then merge the Docs PR. Also do you have twitter handles? I can send out a tweet so people know that it exists |
🎉 This PR is included in version 1.12.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Happy to help! Thank you guys for being so responsive; hope this opens Supabase up to more people. We're @ _mateomorris & Beamanator1 |
fix: supabase#66. Missing redirects on some routes
What kind of change does this PR introduce?
Allows a user to request scopes while signing up/in with an OAuth provider, and returns
provider_token
which allows access to the provider's API.