Routes with extension about sanic-routing

[jacebrowning]

Perhaps something like this?

@app.get("/invoice/<invoice_id:uuid.ext:pdf|txt>")
async def invoice_handler(request, invoice_id, ext):
    ...

Using . as the separator could support all of these patterns:

/foo/<file.ext> # type is assumed to be 'file:str'
/foo/<file.ext:jpg>
/foo/<file.ext:jpg|png|gif|svg>
/foo/<file:uuid.ext>
/foo/<file:path.ext:jpg>
/foo/<file:int.ext:jpg|png|gif|svg>

---

Alternatively, if the file in <file:ext:png> also matched paths (/ character) then that would be sufficient for my use case.

[ahopkins]

I have been looking at this one some more so we can finally wrap it up. The real challenge for me has been to determine what is the appropriate syntax here. While I can appreciate what @jacebrowning offered with file.ext, it really breaks a lot of other patterns and the entire concept that ext is itself the parameter "type".

Therefore, I offer this as the syntax:

/foo/<file:ext> # type is assumed to be 'file:str'
/foo/<file:ext=jpg>
/foo/<file:ext=jpg|png|gif|svg>
/foo/<file=uuid:ext>
/foo/<file=path:ext=jpg>
/foo/<file=int:ext=jpg|png|gif|svg>

[jacebrowning]

How would one specify the type of the file stem?

e.g. To ensure that invoice_id is a UUID and the extension is pdf or text.

[ahopkins]

How would one specify the type of the file stem?

e.g. To ensure that invoice_id is a UUID and the extension is pdf or text.

🤔 Hmm.... that is not something I considered. This implementation would accept anything for the filename. It would be more equivalient to: /<foo>.pdf. Do you have any suggestions on what the implementation could look like?