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
When the value of logout is set to true(which is equivalent to logout: { path: '/logout' }) or is set to a path e.g.logout: { path: '/some-logout-path' } and no such route exists, we could define it automatically from a compiler pass or any another way (ideally with no runtime overhead).
That would remove the error-prone and odd need to declare that route explicitly.
We'd need to make the docs super clear about when one actually needs to define that route explicitly with or without attached controller. Bonus if we can make that route publicly accessible by default, if it doesn't make it too much confusing of course.