[Actix] Type definition overriden when struct used with same name multiple times

[TobiasDeBruijn]

Hey there,

Thanks for all the hard work on Paperclip. I'm using it together with Actix to generate a spec for my API, however I've noticed something odd. Almost every request handler (split out into modules) has a Request and Response struct, for the request and response respectively. However it seems to be only provided once in the final spec.

Assume I have the following two endpoints:

// foo.rs
#[derive(Deserialize, Apiv2Schema)]
pub struct Request {
    a: i32,
    b: i32
}
...

// bar.rs
#[derive(Deserialize, Apiv2Schema)]
pub struct Request {
    c: String,
    d: f64
}

Both API will show the same request struct, rather than foo having it's own, and bar having it's own

Potential solution

I think a potential solution would be to include the module in the definition name, that way you can never have overlap

Versions

actix: 3.3.2
paperclip: 0.6.1
rustc: 1.57.0-beta