1
Better debug behaviour: a single debug session for all calls (I tried `policy: "per-worker"` and it did not do that)
Source: supabase/supabase#36136 · opened by @od-vennre
Hello Supabase community and maintainers.
Edge functions are an odd creation in Supabase. The developer experience is still equally very odd.
The main issue is that in the current model, a new debug session is created for each edge-function call. This makes it very difficult to debug applications with a dozen calls.
Is there a way to create a persistent debug session for all the Supabase edge function calls within a project? This allows the developer to attach the debugger once, and then continue to create breakpoints only in places that they need more clarity on how the execution goes.
I do feel that this is an architectural issue and that the entire edge-function feature is not very well thought out. It shows in many aspects of its use and development. It also feels like a nightmare in production. The system is fragile.
How much negativity can you handle in one issue? The good news, is that I am done for now.
Edge functions are an odd creation in Supabase. The developer experience is still equally very odd.
The main issue is that in the current model, a new debug session is created for each edge-function call. This makes it very difficult to debug applications with a dozen calls.
Is there a way to create a persistent debug session for all the Supabase edge function calls within a project? This allows the developer to attach the debugger once, and then continue to create breakpoints only in places that they need more clarity on how the execution goes.
I do feel that this is an architectural issue and that the entire edge-function feature is not very well thought out. It shows in many aspects of its use and development. It also feels like a nightmare in production. The system is fragile.
How much negativity can you handle in one issue? The good news, is that I am done for now.
No pledges yet. Be the first to back this.
Comments
Similar requests
Add autoRefresh Option to getUser() to Ensure Session Data is Synced with Latest User State
3 votes · 0 comments
Add Feature to Test + Debug Row Level Security Policies
47 votes · 0 comments
OAuth 2.1 server: no way to require MFA (aal2) for OAuth client access tokens
1 vote · 0 comments
Move RLS verification into the policy editor, not beside it
1 vote · 0 comments
[splinter] Proposal: two INFO lints for grant/policy mismatch (privilege_without_policy, policy_without_privilege)
1 vote · 0 comments
No comments yet.