Skip to content

feat: Supabase edge function example#3

Draft
Chriztiaan wants to merge 2 commits into
feat/initfrom
feat/supabase-edge-function
Draft

feat: Supabase edge function example#3
Chriztiaan wants to merge 2 commits into
feat/initfrom
feat/supabase-edge-function

Conversation

@Chriztiaan
Copy link
Copy Markdown
Collaborator

@Chriztiaan Chriztiaan commented May 13, 2026

This PoC takes the original write improvements PoC a step further and wedges the endpoint handling, mapper, and persistence logic into a Supabase edge function.

We get two benefits from this approach compared to the original SupabaseConnector plus Supabase backend:

  • We move all translation/mapping logic from the client to the backend.
  • We get proper transaction support without migrating off Supabase or managing a separate backend (enabling rollback on failure is something the Supabase JS SDK can't do today)
Screenshot 2026-05-13 at 13 00 37

AI disclosure

This PR was created with the help of Claude Code. Help constitutes assistance in research, planning, and rough outline of implementation. Beyond having a hand in the implementation, I have also manually tested this work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant