feat(functions): add region as forceFunctionRegion query parameter #806
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.
Summary
This PR ports the feature from supabase/functions-js#100 to add region as a
forceFunctionRegion
query parameter alongside the existingx-region
header.Changes
FunctionsClient.buildRequest()
to add theforceFunctionRegion
query parameter when a region is specifiedx-region
header andforceFunctionRegion
query parameter are sentx-region
header functionalityImplementation Details
When a region is specified (either in the client or in invoke options), the Functions client now:
x-region
header (existing behavior)forceFunctionRegion
query parameter with the same region value (new behavior)This dual approach ensures better compatibility with edge function routing mechanisms.
Test Plan
testInvokeWithRegion
to verify query parameter is addedtestInvokeWithRegionDefinedInClient
to verify query parameter is added🤖 Generated with Claude Code