[Feature] Fallback route when none match about sanic-routing

[ashleysommer]

Ok, I don't know what I was doing wrong earlier, but I cannot reproduce my issue now.

Now the <path> route always matches last, which is what I wanted.

Note, I also tried it with a regex, like @app.route(r"/<mypath:(.*)>") and that worked fine too (I think regexes are checked after all other route types).

[ahopkins]

Yes, there are actually two different sets of priority for regex routes. "Standard" regex that does not include anything that could potentially match on multiple segments are evaluated inline in the order they would otherwise match. In general, that means most deeply nested first, but it also depends upon the priority of the path parameter type (since, for example a string type could match on both character and numbers).

The exception to the inline matching is when there is a path type or a regex with a /. These are always evaluated last so as to not clobber.

Not sure why you initially experienced an issue since a <path:path> is meant for that purpose and would always be at the end. That makes sense.