docs(auth): correct OAuth grant methods and response shape - #48923
Conversation
|
Thanks for contributing to Supabase! ❤️ Our team will review your PR. A few tips for a smoother review process:
|
|
@lazerg is attempting to deploy a commit to the Supabase Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe OAuth server guide updates grant-listing and revocation method calls. It also updates the documented grant response to use nested client details and the ChangesOAuth grant documentation
Estimated code review effort: 2 (Simple) | ~5 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
I have read the CONTRIBUTING.md file.
YES
What kind of change does this PR introduce?
Docs update.
What is the current behavior?
The OAuth flows guide calls
supabase.auth.oauth.getUserGrants(), which doesn't exist on the client, passes a positional client ID torevokeGrant(), and shows a flat grant object withclient_nameandcreated_at.Fixes #48918
What is the new behavior?
The samples use
listGrants()andrevokeGrant({ clientId }), and the response block matches theOAuthGranttype in@supabase/auth-js: a nestedclientobject plusscopesandgranted_at.Summary by CodeRabbit
listGrants()for retrieving grants.granted_attimestamp.{ clientId }.getUserGrants()method.