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
Hi, I don't know if I am wrong something or there is a bug in the code but if a middleware has a call inside it that decides whether the request of the component passes or not, the middleware does not wait for the response of the call, it temporarily displays the component up a that the call was not answered and then blocks the component and redirects to the page specified in the middleware
With this function I check if a user has verified his mail, before the function goes into the catch, however, it sends me inside my management system, when the answer arrives and it triggers catch, he will go to
return router.push ({name: 'must-be-verified'});
and will update the page with this new route
The text was updated successfully, but these errors were encountered:
Luigidefra
changed the title
middleware with server call is not blocer
middleware with server call is not blocker
Nov 30, 2020
Hi, I don't know if I am wrong something or there is a bug in the code but if a middleware has a call inside it that decides whether the request of the component passes or not, the middleware does not wait for the response of the call, it temporarily displays the component up a that the call was not answered and then blocks the component and redirects to the page specified in the middleware
With this function I check if a user has verified his mail, before the function goes into the catch, however, it sends me inside my management system, when the answer arrives and it triggers catch, he will go to
return router.push ({name: 'must-be-verified'});
and will update the page with this new route
The text was updated successfully, but these errors were encountered: