fix(supabase): ✨ add Supabase Storage adapter and update dependencies#707
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Code Review
This pull request integrates the @vitnode/supabase-storage package into the documentation app, replacing the local storage adapter with the Supabase storage adapter configured via environment variables. Feedback suggests using non-null assertions (!) on the environment variables to prevent potential TypeScript compilation errors when strictNullChecks is enabled.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| adapter: SupabaseStorageAdapter({ | ||
| url: process.env.SUPABASE_URL, | ||
| secretKey: process.env.SUPABASE_SECRET_KEY, | ||
| bucket: process.env.SUPABASE_STORAGE_BUCKET, | ||
| }), |
There was a problem hiding this comment.
Passing process.env variables directly can lead to TypeScript compilation errors if strictNullChecks is enabled, as they are typed as string | undefined but the adapter likely expects string. Using non-null assertions (!) ensures type safety and prevents compilation issues.
| adapter: SupabaseStorageAdapter({ | |
| url: process.env.SUPABASE_URL, | |
| secretKey: process.env.SUPABASE_SECRET_KEY, | |
| bucket: process.env.SUPABASE_STORAGE_BUCKET, | |
| }), | |
| adapter: SupabaseStorageAdapter({ | |
| url: process.env.SUPABASE_URL!, | |
| secretKey: process.env.SUPABASE_SECRET_KEY!, | |
| bucket: process.env.SUPABASE_STORAGE_BUCKET!, | |
| }), |
Improving Documentation
pnpm lint:fixto fix formatting issues before opening the PR.Description
What?
Why?