Add separate function for parsing body in App Router #467
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.
When NextRequest type is added in parseBody function, it is hard to differentiate between NextRequest and NextApiRequest. It cannot be done using
req instanceof NextRequest
because it returnsfalse
even the req type is NextRequest.app/api/webhooks/sanity/route.ts
parseBody.ts
I think it is better to have separate function for parsing body in the App Router route handler. Then we can use the new function to parse body in route handler like this below.
app/api/webhooks/sanity/route.ts