axum-aide api router using axum-typed-routing.

[Jeffr-K]

Here is my code.

#[api_route(POST "/project" { summary: "Creation Project", description: "create project", hidden: false })]
pub async fn create_project(
    Json(adapter): Json<ProjectCreateCommandAdapter>,
    State(_state): State<AppState>
) -> impl IntoApiResponse {
    (StatusCode::CREATED, Json("success.".to_string()))
}

pub fn create_project_docs(item: TransformPathItem) -> TransformPathItem {
    item.operation(|operation| {
        operation
            .description("hello, world")
            .response::<201, Json<String>>()
    })
}

here is my declaration router:

pub async fn initialize_routers() -> ApiRouter {
        let state = AppState::default();  
        let router: ApiRouter = ApiRouter::new()
            .typed_api_route_with(create_project, create_project_docs).with_state(state.clone());
        router
    }

This is my error on console:

#[api_route(POST "/project" { summary: "Creation Project", description: "create project", hidden: 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the trait `Handler<_, _>` is not implemented for fn item `fn(extractor::Json<ProjectCreateCommandAdapter>, axum::extract::State<AppState>) -> impl std::future::Future<Output = impl IntoApiResponse> {__inner__function__}`

The error is caused by Json(adapter): Json<ProjectCreateCommandAdapter>. if It is removed, it would be work well.

What's wrong with me?

[tamasfe]

Does ProjectCreateCommandAdapter implement JsonSchema and Deserialize?

[Jeffr-K]

Thank you really quick answer to me :)

A) Yes. I did.

here is my DTO:

use schemars::JsonSchema;

#[derive(Debug, Deserialize, JsonSchema)]
pub struct ProjectCreateCommandAdapter {
     #[serde(rename = "projectName")]
     pub project_name: String
}

[Jeffr-K]

The json type is custom json type like this not json_schema

use aide::operation::OperationIo;
use axum::extract::FromRequest;

use axum::response::IntoResponse;
use axum_jsonschema::JsonSchemaRejection;

use serde::Serialize;
use serde_json::json;

use crate::infrastructure::configuration::docs::app_error::AppError;

#[derive(FromRequest, OperationIo)]
#[from_request(via(axum::Json), rejection(AppError))]
#[aide(input_with = "axum::Json<T>", output_with = "axum::Json<T>", json_schema)]
pub struct Json<T>(pub T);

impl<T> IntoResponse for Json<T> where T: Serialize {
    fn into_response(self) -> axum::response::Response {
        axum::Json(self.0).into_response()
    }
}

impl From<JsonSchemaRejection> for AppError {
    fn from(rejection: JsonSchemaRejection) -> Self {
        match rejection {
            JsonSchemaRejection::Json(j) => Self::new(&j.to_string()),
            JsonSchemaRejection::Serde(_) => Self::new("invalid request"),
            JsonSchemaRejection::Schema(s) => {
                Self::new("invalid request").with_details(json!({ "schema_validation": s }))
            }
        }
    }
}

[tamasfe]

I don't see anything wrong, so this could be axum's extractor order: https://docs.rs/axum/latest/axum/extract/index.html#the-order-of-extractors

[dzmitry-lahoda]

there is more "official" routing for axum https://docs.rs/axum-extra/latest/axum_extra/routing/trait.TypedPath.html .

it may be worth looking for integration imho.