Fix validation, middleware, and client typing regressions#72
Merged
Conversation
Copilot created this pull request from a session on behalf of
aryansondharva
May 28, 2026 05:11
View session
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The repo had a mix of failing backend schema checks, broken middleware exports, and a few high-signal client lint/type regressions. The affected paths now align with the expected constraints and runtime behavior again.
Backend validation
Middleware
middlewareexport for CORS handling.Supabase client surface
backend/lib/supabaseindex module with the server/client helpers expected by consumers and tests.Client cleanup
anyfrom the touched auth/API paths.Example: