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.
There's currently a bug where when an authenticated user visits /login, the authLayout component renders as a result of the /login route being bound by the Admin component in the created() lifecycle method, triggering a missing va prop error.
Describe the solution you'd like
Investigate if the va prop should be set during the routes binding or we keep it as a responsibility of the Unauthenticated component to render the provided authLayout with the on the run created va prop.
Despite the choice selected, an authenticated user should not be able to visit the /login route. A redirection must be set in the route hooks module
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
There's currently a bug where when an
authenticated
user visits/login
, theauthLayout
component renders as a result of the/login
route being bound by theAdmin
component in thecreated()
lifecycle method, triggering a missingva
prop error.Describe the solution you'd like
Investigate if the
va
prop should be set during the routes binding or we keep it as a responsibility of theUnauthenticated
component to render the providedauthLayout
with the on the run createdva
prop.Despite the choice selected, an authenticated user should not be able to visit the
/login
route. A redirection must be set in theroute hooks
moduleThe text was updated successfully, but these errors were encountered: