-
-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
json()
should also accept a status
option
#4
Comments
Sounds like a nice addition. |
@smeijer I've seen that you've already implemented Responses from |
Correct, I haven't published yet, and want to add a few tests before I do so. But it should be possible with the version on |
Published as https://github.com/smeijer/next-runtime/releases/tag/v1.2.0. I'll work on the docs later, but here's an example: next-runtime/src/responses.test.ts Lines 78 to 82 in 7ccae3e
|
A 200 status for all responses works, but being able to give a 4xx for bad responses would definitely feel more proper
The text was updated successfully, but these errors were encountered: