[6.15] How to access to Extension in Leptos_Axum

[SoapyDev]

Good day,

I looked everywhere I could, but could not find an answer.

Hopefully this is a problem on my side and not one on the framework, or its already fixed in 7.1.

I am attempting to retrieve in a handler a user that was extracted from my database in my middlewear.
In axum I could do it this way (per their documentation) :

async fn extension(Extension(state): Extension<State>) {}

#[derive(Clone)]
struct State { /* ... */ }

So, based on this example and the section on extractors in the leptos book, I would expect this pattern to work.

#[cfg(feature = "ssr")]
pub async fn my_middlewear(
   /* ... */
    mut request: Request,
    next: Next,
) -> Result<impl IntoResponse, HttpError> {  
    /* ... */
    // Insert the user into the request
    request.extensions_mut().insert(user);
    Ok(next.run(request).await)
}

  #[server]
  pub async fn get_user_handler() -> Result<User, ServerFnError> {
      use axum::extract::Extension;
      use leptos_axum::extract;
  
      let Extension(user) : Extension<User> = extract()
          .await
          .map_err(|_| ServerFnError::new("User not found".to_string()))?; 
      
      Ok(user)
  }

What I get as a result is : "should have had Parts provided by the leptos_axum integration" that I can be found in :

leptos/integrations/axum/src/lib.rs

Line 1972 in f9533ab

"should have had Parts provided by the leptos_axum integration",

Am I missing something ?

Thanks for your time,

[gbj]

Hi -- Sorry for the delayed response. I don't have enough experience with Axum extensions or middleware to know whether extensions would behave differently from any other extractor in this situation. That said, the error message here doesn't have to do with the extractor itself, and it would actually bail out before the extractor even runs. I have not seen reports of similar issues, so you may be looking in the wrong place. (For example, are you using a custom handler or something similar that doesn't provide Parts via context as expected?)

I'm happy to look at a minimal reproduction at some point if you have one, but I don't think there's much more I can say than the above for now.