I wanted to ask whether you would be open for a pull request that would make `r.rodauth` automatically route routes with a path prefix, without the need for `r.on "<prefix>"`. It would of course keep backwards compatibility for apps using `r.on "<prefix>"`.
The reason I would like to make this change is because e.g. `r.on "auth"` will by default not allow the main app to define its own "auth/*" routes when the Rodauth app is used as a middleware, unless the `r.on` block explicitly marks the request as not handled, either using the pass plugin or by throwing `:next` as you had suggested
. While both solutions work, they do require the user to know more about Roda routing, and I'm trying to find alternatives which would minimize the learning curve.
Updating the documentation would definitely help, but I thought it would be convenient in general if we could remove this extra step, so that all that's needed to add a path prefix is changing the `prefix` setting. Personally, I'm often forgetting to update the `r.rodauth` call after setting a `prefix`, so I definitely see an opportunity here for improved ergonomics :)
Let me know what you think.