TypedPath with extractors like Query, ContentLengthLimit etc

[BratSinot]

Greetings!

Does axum-extra TypedPath macro can't work with extractors? I'm getting errors:

error[E0277]: the trait bound `axum::extract::ContentLengthLimit<axum::extract::Query<Param>, 1024_u64>: axum_extra::routing::TypedPath` is not satisfied
   --> <...>
    |
19  |         .typed_post(move |param| handle(param, context))
    |          ^^^^^^^^^^ the trait `axum_extra::routing::TypedPath` is not implemented for `axum::extract::ContentLengthLimit<axum::extract::Query<Param>, 1024_u64>`
    |
    = help: the trait `axum_extra::routing::TypedPath` is implemented for `Param`
note: required by a bound in `axum_extra::routing::RouterExt::typed_post`
   --> <...>/axum-extra-0.3.6/src/routing/mod.rs:102:12
    |
102 |         P: TypedPath;
    |            ^^^^^^^^^ required by this bound in `axum_extra::routing::RouterExt::typed_post`

[BratSinot]

Okey, seems what problem in param struct:

#[derive(TypedPath, Deserialize)]
#[typed_path("/env_vars/rust_log")]
pub struct Param {
    rust_log: SmolStr,
}

19 | #[typed_path("/env_vars/rust_log")]
   |              ^^^^^^^^^^^^^^^^^^^^ missing field `rust_log`
   |
help: include the missing field in the pattern
   |
19 | #[typed_path("/env_vars/rust_log" { rust_log })]
   |                                   ++++++++++++
help: if you don't care about this missing field, you can explicitly ignore it
   |
19 | #[typed_path("/env_vars/rust_log" { .. })]

[BratSinot]

Ow, I think I got it. No way to use TypedPath with closure captures like this?
https://docs.rs/axum/latest/axum/index.html#using-closure-captures

[BratSinot]

#[derive(Deserialize)]
pub struct Param {
    rust_log: SmolStr,
}

#[derive(Deserialize, TypedPath)]
#[typed_path("/env_vars/rust_log")]
pub struct UpdateFilterPath;

<...>

.typed_post(move |path, param| handle(path, context, param))

[davidpdrsn]

The extractors don't go inside the struct. That's for path params like /env_vars/:rust_log (note the colon).

The extractors go in the function signature like any other extractor.

Ow, I think I got it. No way to use TypedPath with closure captures like this?

That should just work like normal.