Parsing a Path parameter with a trailing extension

[sunli829]

Discussed in #380

^{Originally posted by phaer September 2, 2022}
Hello,

I am trying to use a Route like "/notebooks/:id.pdf but, it seems that poetry interprets this as a parameter called "id.pdf" instead of an parameter "id", followed by the string ".pdf". Using a regex like /notebooks/:id<[^\\.]>.pdf does not work as expected either.

Swagger UI confirms that the parameters aren't interpreted as expected:

Is this something supported by poem? Am I missing something?

[sunli829]

I reviewed the code, this is not a bug, the current matching algorithm cannot support extensions.

I need to think about how to do it. 😀

[sunli829]

I thought about it and suggested the following solution:

#[oai(path = "/notebooks/:id")]
async fn handler(id: Path<String>) -> Result<()> {
    if id.ends_with(".svg") {
        // do something
    } else {
        Err(Error::from_status(StatusCode::NotFound))
    }
}

[phaer]

Thanks for the quick response! But its more a work-around than a solution in my opinion as, ideally, I'd like to have three different handlers: "/notebooks/:id", "/notebooks/:id.pdf" and "/notebooks/:id.png". With this work-around one has to cram all 3 of them into a single handler and do the rest of the matching myself.