fix(nextjs): Update clerkMiddleware request callback to accept an async function
#5154
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.
Description
Portrait #5147
Context
The ability to set
clerkMiddlewareoptions with a request callback was introduced here, to cover the cases of setting a satellite domain based on the incoming host.However, the logic was only tested as synchronously accessing the request, and we forgot to support the callback to be async to cover the other cases as fetching options from an external data source.
The above is indicated in our docs as "dynamically":
Checklist
pnpm testruns as expected.pnpm buildruns as expected.Type of change