Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@katowulf - This is my second attempt at fixing #431. My fix last time made the login event not fire after a user logs out. This is because of some hacky code we had in place to suppress multiple logout events firing. This code is not very easy to understand and is actually not necessary anymore. I added a check to logout to not fire the logout event if no user is actually logged in. This seems logical to me and I'm surprised Simple Login itself doesn't do this. This is not a breaking change since the behavior from calling
$logout()
twice was already busted.Note that
this._currentUserData
will get set tonull
within_onLoginEvent()
which will get fired by the call to Simple Login'slogout()
. As a result, we no longer need to set it tonull
within$logout()
itself.cc/ @davideast