This repository was archived by the owner on May 13, 2023. It is now read-only.
feat: custom HTTP method for function invoke #16
Merged
Conversation
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
dshukertjr
approved these changes
Feb 12, 2023
There was a problem hiding this comment.
@gabfeudo Legend! Thanks for this one!
Currently, js SDK doesn't have support for other HTTP methods, so checked with the Functions team to see if js SDK has plans on supporting other HTTP methods, and the answer was yes, so adding this to the Flutter SDK!
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What kind of change does this PR introduce?
Possibility to choose HTTP method for Edge Functions invoke.
What is the current behavior?
Developers can't choose what HTTP method use when invoking Edge Functions