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
Is your feature request related to a problem? Please describe.
The logoffLocal() function is asynchronous internally, even though it looks synchronous on the outside (it returns void). In the angular app that I'm currently working with, we have a forced reload of the page right after calling this function, which cancels everything that is currently going on. Meaning, when the page reloads, the current user is still logged in because logoffLocal() didn't have time to finish. This is a race condition, the behavior is inconsistent between browsers and mainly appears on Firefox (in our case).
Describe the solution you'd like
Like asynchronous functions usually do, it should return a promise or an observable, which would signal the user when the function has done its thing. It wouldn't even be a breaking change, since the user could just ignore the return value and use the function the same way as today.
Describe alternatives you've considered
Currently we have a fixed delay after the function, to give it time to finish, but that feels really awkward and clunky, not the way things should be done.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The logoffLocal() function is asynchronous internally, even though it looks synchronous on the outside (it returns void). In the angular app that I'm currently working with, we have a forced reload of the page right after calling this function, which cancels everything that is currently going on. Meaning, when the page reloads, the current user is still logged in because logoffLocal() didn't have time to finish. This is a race condition, the behavior is inconsistent between browsers and mainly appears on Firefox (in our case).
Describe the solution you'd like
Like asynchronous functions usually do, it should return a promise or an observable, which would signal the user when the function has done its thing. It wouldn't even be a breaking change, since the user could just ignore the return value and use the function the same way as today.
Describe alternatives you've considered
Currently we have a fixed delay after the function, to give it time to finish, but that feels really awkward and clunky, not the way things should be done.
The text was updated successfully, but these errors were encountered: