You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When returning the attribute statusCode in a seneca reply with an HTTP status code value representing an error (e.g. 401), seneca produces an error.
See the example below.
I'm not sure if this is expected behavior or not, but it was an unexpected result for me as a developer and took a bit to track down. To me, seneca should only produce an error if I return a value in the error parameter. Everything in the reply parameter should just be passed along.
When returning the attribute
statusCode
in a seneca reply with an HTTP status code value representing an error (e.g.401
), seneca produces an error.See the example below.
I'm not sure if this is expected behavior or not, but it was an unexpected result for me as a developer and took a bit to track down. To me, seneca should only produce an error if I return a value in the error parameter. Everything in the reply parameter should just be passed along.
Example Code:
Server.js
Server Output
Starting the server side.
Client.js
Client Output
Starting the client side and acting on a pattern.
The text was updated successfully, but these errors were encountered: