-
-
Notifications
You must be signed in to change notification settings - Fork 796
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
Status codes are not being picked up from error message #108
Comments
OK. will need to review. I think this could be implemented by changing the offline response template. |
Wow this is great, which serverless version? |
The docs for it are here: https://serverless.com/framework/docs/providers/aws/events/apigateway/ under "Using status codes" |
Fixed in v3.2! |
Sorry @dherault, but I've just installed 3.2.1 and it's not fixed, at least when using traditional |
I thought I'd be the case sorry! Reopening u_u |
serverless now promotes a convention that if you throw a error with a message like "[404] Not Found", it will set the status code appropriately.
Offline is not picking up on this convention.
The text was updated successfully, but these errors were encountered: