[BREAKING] Only match non-empty string

[ahopkins]

Stemming from the conversation here: sanic-org/sanic-guide#92

This is a BREAKING change.

This this change, these will NOT match on an empty string.

router.add("/<foo>", ...)
router.add("/<foo:str>", ...)

This also adds <foo:strorempty> to allow for matching empty str patterns.

[Tronic]

I suspect that this might be a breaking change for many who actually depend on str matching empty strings but I am still in favour of breaking it and having people migrate to strorempty or separate handlers/routes for such use cases.

Is this strorempty only supposed to be usable as the final part of an URL where the route has no trailing slash? Because you cannot have // in a path anyway, so I don't see where else this could be used.

EDIT: Turns out that HTTP actually allows consecutive slashes in path part of URLs, although I do expect those to break in many places. Nginx handles them as a single slash for file paths but logs and proxies keeping the multiple slashes.

[Tronic]

LGTM but suggesting further consideration and documentation prior to merge (but with inclusion in 22.3).

[ashleysommer]

Good change