Router re-export can cause confusion

[davidpdrsn]

axum's Router is generic over the request body but it defaults the type parameter to axum::body::Body (hyper's body type). However that isn't compatible with this library which requires axum::body::BoxBody such that middleware can more easily change the request body type. Typing axum::Router<axum::body::BoxBody> is tedious so we've added this re-export:

pub type Router<B = BoxBody> = axum::Router<B>;

However that means there are now two routers to know about: the one in axum and one in this library. They're subtly different because Server::with doesn't support axum::Router but it does support server_framework::Router.

All this can be very confusing to new users who aren't familiar with the ecosystem and things fit together.

We should consider ways to fix, or least alleviate this.

[davidpdrsn]

I have found a good solution to this that fixes the root cause in axum.

Relevant PRs:

• Remove request body type param tokio-rs/axum#1154
• feat(body): add Body::wrap_body hyperium/hyper#2913