Refactor: Remove orphaned Supabase ai-chat edge function (Fixes #854)#977
Conversation
|
@ArshVermaGit is attempting to deploy a commit to the durdana3105's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
📝 WalkthroughWalkthroughThe entire Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
ArshVermaGit
left a comment
There was a problem hiding this comment.
issue resolved
This PR addresses the architectural technical debt outlined in issue #854 by completely removing the unused and fragmented Supabase ai-chat edge function. Because the client exclusively uses the custom Node.js Express backend (/api/ai/*) for OpenRouter AI integrations, the Edge Function was orphaned, creating duplicated logic (like token validation and prompt sanitization) and potential maintenance/security liabilities. By removing supabase/functions/ai-chat, this PR successfully enforces a single source of truth and strictly centralizes all API handlers within our Express backend.
Closes #854
Summary by CodeRabbit