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
I am in the process of trying to adopt leptos into my axum & aide server but i'm facing difficulties because aide requires you to attach the transformation to a route via ApiRouter.api_route which also adds the handler. But I don't want to use ApiRouter to define my routes because leptos does not implement their necessary trait for it, only for axum's Router. I want to be able to attach my get_docs etc. transformation functions to an existing route in the router without having to use the ApiRouter's route definition methods. This way, I can let leptos define my routers and then tag documentation to them later via the from method for ApiRouter from a Router. Is this currently possible? You can see how I'm doing it now (without leptos):
Ideally I think it would be best if I didn't need to depend on using ApiRouter to add documentation to the axum router, rather just implementing traits or something instead.
The text was updated successfully, but these errors were encountered:
I am in the process of trying to adopt
leptos
into myaxum
&aide
server but i'm facing difficulties becauseaide
requires you to attach the transformation to a route viaApiRouter.api_route
which also adds the handler. But I don't want to useApiRouter
to define my routes becauseleptos
does not implement their necessary trait for it, only foraxum
'sRouter
. I want to be able to attach myget_docs
etc. transformation functions to an existing route in the router without having to use theApiRouter
's route definition methods. This way, I can letleptos
define my routers and then tag documentation to them later via thefrom
method forApiRouter
from aRouter
. Is this currently possible? You can see how I'm doing it now (withoutleptos
):But I want something like:
Ideally I think it would be best if I didn't need to depend on using
ApiRouter
to add documentation to theaxum
router, rather just implementing traits or something instead.The text was updated successfully, but these errors were encountered: