Quite said to see it go.
I used to use this.resource to define dashboard resource that has AuthenticatedOnlyMixin and protects all its childs against unauthenticated access. Currently, after converting to route, not only all my routes are now prefixed with dashboard.... but also I have one extra level of directories in both controllers and routes folder…
I’ve also used it to define dashboard specific layout (think of it as a application but only for authenticated users) that I was unable to put into application template due to login/register pages having a different theme.
Any better workaround?
Defining Authenticated only mixing on every single top-level route inside a dashboard route just feels wrong to me.