Duplicate handlers do not cause a compilation error

[szagi3891]

Expected Behavior

I would expect that the macro would not allow this code to compile

Actual Behavior

When we have duplicate handlers, the code compiles.

    #[oai(method = "get", path = "/fun1")]
    async fn fun1(&self) -> PlainText<String> {
        PlainText("response from fun1".into())
    }

    #[oai(method = "get", path = "/fun1")]
    async fn fun2(&self) -> PlainText<String> {
        PlainText("response from fun2".into())
    }

Steps to Reproduce the Problem

1. You have to clone https://github.com/szagi3891/poem-test
2. And then run with cargo run

Specifications

• Version: poem = "1.0.38", poem-openapi = "1.0.41"
• Platform: MacOs
• Subsystem:

[sunli829]

I cannot detect duplicate paths at compile time, but I can panic at runtime.

[szagi3891]

@sunli829 Is it possible to make this panic happen when starting the application?

[sunli829]

Yes. If there are duplicate paths, a panic will occur when starting the application. 🙂

[sunli829]

Released in v1.2.6

[szagi3891]

Something is still not working. Here I have an example of such duplicate handlers:
https://github.com/szagi3891/poem-test/blob/master/src/main.rs#L142

When I run cargo run, the server gets up (no panic). And it should panic with a message that "GET /fun1" is duplicated

[sunli829]

This can be detected in the macro, I forgot to do this. 🙂

[sunli829]

Fixed in v1.2.7

[szagi3891]

Fantastic. It works perfectly. Thank you very much :)