Skip to content

Support extra HTTP methods in edge function invocation #1372

@nadav7679

Description

@nadav7679

Description

Hi all,

When invoking an edge function through the client, the 'POST' method is hardcoded in both the sync and async clients. Our edge function also accepts PUT/DELETE HTTP methods, which makes the supabase client unusable to us.

Suggested solution

The internal _request method already supports different HTTP methods, so I suggest adding a method argument to the invoke method with a default to "POST", and propagating this argument to _request.

Thanks!

Alternatives

No response

Additional context

No response

Metadata

Metadata

Assignees

Labels

FeaturepythonPull requests that update Python code
No fields configured for Feature.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions