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
Is your feature request related to a problem? Please describe. There's currently a bug where when an
authenticateduser visits/login, theauthLayoutcomponent renders as a result of the/loginroute being bound by theAdmincomponent in thecreated()lifecycle method, triggering a missingvaprop error.Describe the solution you'd like Investigate if the
vaprop should be set during the routes binding or we keep it as a responsibility of theUnauthenticatedcomponent to render the providedauthLayoutwith the on the run createdvaprop. Despite the choice selected, an authenticated user should not be able to visit the/loginroute. A redirection must be set in theroute hooksmodule