A lot of discussions have come up regarding pages:
It's weird that pages inherit from rio.Component, rather than rio.Page. It's even more confusing, that in addition to the component there is a rio.Page object, but that one only stores metadata.
Redirects are an often needed feature. While they can be implemented using Guards, doing so is rather ugly. Add a proper rio.Redirect class.
Instead of specifying all pages in an app, find them automatically from the pages directory.
A lot of discussions have come up regarding pages:
It's weird that pages inherit from
rio.Component, rather thanrio.Page. It's even more confusing, that in addition to the component there is ario.Pageobject, but that one only stores metadata.Redirects are an often needed feature. While they can be implemented using Guards, doing so is rather ugly. Add a proper
rio.Redirectclass.Instead of specifying all pages in an app, find them automatically from the
pagesdirectory.Anything else?