Purpose of TypedPath struct?

[gpluscb]

Hi, I'm confused what is the purpose of the TypedPath struct.
I assumed from the docs you could use it in your handler to not have to manually implement OperationInput on all paths.
However this is impossible since TypedPath does not implement the TypedPath trait or JsonSchema.

For this example code the compiler complains that these traits are not implemented:

use aide::axum::{ApiRouter, routing::typed::TypedPath as AideTypedPath};
use axum_extra::routing::TypedPath;
use schemars::JsonSchema;
use serde::{Deserialize, Serialize};

fn router() -> ApiRouter {
    ApiRouter::new().typed_get(handler)
}

#[derive(TypedPath, Serialize, Deserialize, JsonSchema)]
#[typed_path("/handler/{id}")]
struct HandlerPath {
    id: u64,
}

async fn handler(
    AideTypedPath(HandlerPath { id }): AideTypedPath<HandlerPath>,
) -> &'static str {
    "Handler"
}

Is there a different purpose to this struct or a different way to use typed routing without having to implement/derive OperationInput for all paths?

[jplatte]

Hey. I don't have much time to improve documentation at the moment or to dive into your code sample and understand what's wrong, but maybe the discussion that happened around this before it was implemented (here will be helpful to you?