-
-
Notifications
You must be signed in to change notification settings - Fork 11.4k
docs: Add Expo quick start guide #40744
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
Conversation
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
6 Skipped Deployments
|
|
Thanks! Will get to this, but also have something of an internal planning and strategy around which frameworks to support, how to add them across the docs, etc… |
WalkthroughAdded an Expo React Native quickstart: a new navigation entry and a new MDX guide with a seven-step workflow for integrating Supabase into Expo projects. Also removed a triple-slash type reference from the docs next-env declaration. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
🧰 Additional context used🧠 Learnings (5)📚 Learning: 2025-12-11T02:39:49.745ZApplied to files:
📚 Learning: 2025-12-11T02:39:45.932ZApplied to files:
📚 Learning: 2025-12-11T16:46:18.690ZApplied to files:
📚 Learning: 2025-12-11T16:46:18.690ZApplied to files:
📚 Learning: 2025-12-11T16:46:18.690ZApplied to files:
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
Comment |
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: 4
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (3)
apps/docs/components/Navigation/NavigationMenu/NavigationMenu.constants.ts(1 hunks)apps/docs/content/guides/getting-started/quickstarts/expo-react-native.mdx(1 hunks)apps/docs/next-env.d.ts(0 hunks)
💤 Files with no reviewable changes (1)
- apps/docs/next-env.d.ts
🧰 Additional context used
🧠 Learnings (2)
📚 Learning: 2025-12-11T02:39:49.745Z
Learnt from: CR
Repo: supabase/supabase PR: 0
File: .cursor/rules/docs-test-requirements.mdc:0-0
Timestamp: 2025-12-11T02:39:49.745Z
Learning: Applies to apps/docs/**/*.{test,spec}.ts : Before running tests in the docs application, check Supabase status using `pnpm supabase status`. If Supabase is not running, start it with `pnpm supabase start`. Reset the database with `pnpm supabase db reset --local` to ensure clean state. Run tests using `pnpm run -F docs test:local:unwatch` (without watch mode)
Applied to files:
apps/docs/content/guides/getting-started/quickstarts/expo-react-native.mdx
📚 Learning: 2025-12-11T02:39:45.932Z
Learnt from: CR
Repo: supabase/supabase PR: 0
File: .cursor/rules/docs-graphql.mdc:0-0
Timestamp: 2025-12-11T02:39:45.932Z
Learning: Applies to apps/docs/resources/**/[!Schema]*Resolver.ts : Use `supabase()` client for database operations with `convertPostgrestToApiError` for error handling in GraphQL resolvers
Applied to files:
apps/docs/content/guides/getting-started/quickstarts/expo-react-native.mdx
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: build
- GitHub Check: typecheck
🔇 Additional comments (2)
apps/docs/components/Navigation/NavigationMenu/NavigationMenu.constants.ts (1)
358-361: LGTM!The navigation entry is correctly structured and follows the existing pattern. The URL path aligns with the new MDX documentation page added in this PR.
apps/docs/content/guides/getting-started/quickstarts/expo-react-native.mdx (1)
190-192: The URL paths in the Next steps section are correct and consistent with all other quickstart guides. All quickstart files (hono, nextjs, reactjs, sveltekit, expo-react-native) use the same/docs/guides/...format. The different pattern in NavigationMenu.constants.ts (/guides/...) is intentional—it's client-side navigation where Next.js automatically prepends the basePath (/docs), while static MDX content requires the full path. No broken links exist.Likely an incorrect or invalid review comment.
apps/docs/content/guides/getting-started/quickstarts/expo-react-native.mdx
Show resolved
Hide resolved
apps/docs/content/guides/getting-started/quickstarts/expo-react-native.mdx
Show resolved
Hide resolved
apps/docs/content/guides/getting-started/quickstarts/expo-react-native.mdx
Show resolved
Hide resolved
apps/docs/content/guides/getting-started/quickstarts/expo-react-native.mdx
Show resolved
Hide resolved
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 made some minor changes in a commit to add some new elements we've added to other quickstarts, apart from that 🚀
I have read the CONTRIBUTING.md file.
YES
What kind of change does this PR introduce?
We have most of the major frameworks that we support, but we are missing Expo. In my opinion, Expo is an important one that we should have covered. This PR adds it.
Summary by CodeRabbit
New Features
Documentation
Chores
✏️ Tip: You can customize this high-level summary in your review settings.