fix(functions): missing body when Content-Type header supplied by dev #1758
+3
−0
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.
Moved from: supabase/functions-js#90
Author: @ggaabe
What kind of change does this PR introduce?
Fixes null body when user supplies
Content-Type
in headers ofsupabase.functions.invoke
, ie: invoked like thisWhat is the current behavior?
The request
body
sent over the network will be null, instead of the supplied body value, if a Content-Type header is suppliedPlease link any relevant issues here.
What is the new behavior?
If user supplies a
Content-Type
header, the body will contain its original value supplied by the developer