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
If a request has no session token, then we do return reply(Boom.unauthorized()), but that only calls the next .then callback and sets session in it to Boom.unauthorized().
We have to throw an error instead and set error.status to 404 so that the .catch callback can take care of it
The text was updated successfully, but these errors were encountered:
A corollary to this is the other line from the same function that does return reply.continue(), also resulting in an erroneous call to the next handler in the promise chain.
Yes, this is indeed now resolved, though the test suite is still throwing out a warning as a result of jupiter/simple-mock#22. I'll update the above PR to fix this only.
If a request has no session token, then we do
return reply(Boom.unauthorized())
, but that only calls the next.then
callback and setssession
in it toBoom.unauthorized()
.We have to throw an error instead and set
error.status
to 404 so that the.catch
callback can take care of itThe text was updated successfully, but these errors were encountered: