-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
Clarifying OAuth usage #15781
Clarifying OAuth usage #15781
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Caution Review failedThe pull request is closed. WalkthroughThis pull request makes several documentation updates. It removes the "troubleshooting" section from the exported metadata file, updates a bullet point in a docs page to include a hyperlink, revises table headers and row details in another docs file to clarify OAuth client information, and adds a rewrite rule in the Vercel configuration to map an old troubleshooting path to a new location. Changes
Possibly related PRs
Suggested labels
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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.
Actionable comments posted: 0
🧹 Nitpick comments (1)
docs-v2/pages/connect/managed-auth/oauth-clients.mdx (1)
21-28
: Improve Table Clarity and Correct Typographical Error
The table now better distinguishes between the use of Pipedream’s OAuth client versus a custom client by updating the header and the operational details. However, there is a typographical error in the "Retrieve user credentials" row ("credentrials" should be "credentials"). Consider applying the following change:- | Retrieve user credentrials | [Fetch the credentials](/connect/api#accounts) for your end user from Pipedream's API to use in your app | ❌ Pipedream<br />✅ Custom | + | Retrieve user credentials | [Fetch the credentials](/connect/api#accounts) for your end user from Pipedream's API to use in your app | ❌ Pipedream<br />✅ Custom |This refinement will further improve the professionalism and clarity of the documentation.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (4)
docs-v2/pages/connect/_meta.tsx
(0 hunks)docs-v2/pages/connect/index.mdx
(1 hunks)docs-v2/pages/connect/managed-auth/oauth-clients.mdx
(1 hunks)vercel.json
(1 hunks)
💤 Files with no reviewable changes (1)
- docs-v2/pages/connect/_meta.tsx
⏰ Context from checks skipped due to timeout of 90000ms (3)
- GitHub Check: pnpm publish
- GitHub Check: Lint Code Base
- GitHub Check: validate-links
🔇 Additional comments (3)
docs-v2/pages/connect/index.mdx (1)
21-21
: Enhance Navigation with Hyperlink Update
The updated bullet now provides a clear, clickable link to the pre-built tools and triggers. This improves usability by directing users to the relevant components page, ensuring a smoother experience.vercel.json (1)
232-235
: New Rewrite Rule for Troubleshooting Documentation
A new rewrite rule has been introduced to redirect/docs/connect/troubleshooting
to/docs/connect/managed-auth/troubleshooting
. This change aligns with the recent reorganization of the documentation and ensures that users looking for troubleshooting content are properly guided. Please verify that all related links and references in the docs are updated accordingly.docs-v2/pages/connect/managed-auth/oauth-clients.mdx (1)
15-17
: Clarify Callout Messaging on OAuth Clients
The callout message now emphasizes that users can always opt to use their own OAuth client. This improvement provides clearer guidance on production considerations regarding OAuth clients. Ensure that similar guidance is consistently presented across related documentation.
WHY
Summary by CodeRabbit