Path impl_for override. PathBuilder::path_from

[wyatt-herkamp]

I personally do like the derive OpenAPI macro

So I tend to implement OpenAPI by hand.

However it generates a pretty ugly to look at type __path_{function_name} I use Actix so Actix already generates a type for my route. So I just want the path macro to implement for that type.

Example

#[utoipa::path(get,  
    impl_for = me,  
    path = "/api/me",  
    responses(  
        (status = 200, description = "You are Logged In", body = User),  
        (status = 401, description = "You are not logged in")  
    ),  
    security(  
        ("api_key" = [])  
    )  
)]  
#[get("")]  
pub async fn me(auth: Authentication) -> JsonResponse<User> {  
    JsonResponse::from(Into::<User>::into(auth))  
}  

Then I added a new function to PathBuilder path_from. Just for a cleaner way of appending a path.

[juhaku]

However it generates a pretty ugly to look at type __path_{function_name}

It generates ugly to look so that it does not name clash even possibly with any other type that might be generated. However as it is a generated type it does not really matter what it looks like though. But I can see why somebody would save a few bytes without generating an "extra" type. Yet this actually could open a door for path support in traits as well.