David Pedersen

I still think that would require getting the `MethodRouter` at a given route, from `Router`. So before adding `/a/` we could check if there already is something at that route...

For me rust-analyzer still checks all the examples which I'd like to avoid. I tried a bunch of ways to set `overrideCommand` (both `rust-analyzer.cargo.buildScripts.overrideCommand` and `rust-analyzer.checkOnSave.overrideCommand`) but couldn't get it...

I agree that using `Path

I'm a little afraid of this since we used to require `Sync` in the past but reverted it because it broke other stuff (https://github.com/tokio-rs/axum/pull/273). At least requires a bunch of...

I'll also test it with our stuff at Embark.

Can you explain what you use case is for this?

For future readers, here is how to do it today: ```rust async fn upload_json(mut multipart: Multipart) -> Result { #[derive(serde::Deserialize)] struct Payload { foo: String, } while let Some(field) =...

I'll close this for now. Not clear what the use case is so @affanshahid please comment if you can provide more context.

This is a limitation with how nesting works. Since nested routers internally use wildcards you need to add the layer to the inner router as well. I have spent quite...

The root issue is that when your middleware is called all we know is that the prefix for some nested router matched. Since the middleware is on the outer most...