Improve NextApiResponse typing #7841
Merged
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.
Introducing two changes here
Fix NextApiResponse.status type signature 989e549
According to the doc we can chain the function call (thanks to here)
Improve NextApiResponse typing fb11fd2
Makes the NextApiResponse accept a type argument
Currently
res.json(...)
is not type checked but it could be helpful to see at a glance the handler signature, like so:I didn't make the NextApiRequest generic because—we can't trust the request input—we would have to validate it anyway.
What do you think ?