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
I'm reading through the code debugging an issue and I note that in request.js the req.logOut function calls this._passport.instance._sm.logOut(this), which can take a callback parameter, but none is passed. Granted, I'm sure this is because req.logOut doesn't take any arguments, but that seems like a failure.
A passport strategy's logout may require async tasks to be completed (the case I'm debugging) or otherwise have use for a callback function. Shouldn't req.logOut take a callback argument and then pass it to this._passport.instance._sm.logOut, which already has logic to call it?
Expected behavior
I would expect a way to get a callback called after being logged out.
Actual behavior
A callback can't be provided, and thus isn't called.
I'm reading through the code debugging an issue and I note that in
request.js
thereq.logOut
function callsthis._passport.instance._sm.logOut(this)
, which can take a callback parameter, but none is passed. Granted, I'm sure this is becausereq.logOut
doesn't take any arguments, but that seems like a failure.A passport strategy's logout may require async tasks to be completed (the case I'm debugging) or otherwise have use for a callback function. Shouldn't
req.logOut
take a callback argument and then pass it tothis._passport.instance._sm.logOut
, which already has logic to call it?Expected behavior
I would expect a way to get a callback called after being logged out.
Actual behavior
A callback can't be provided, and thus isn't called.
Steps to reproduce
Environment
The text was updated successfully, but these errors were encountered: