Invalid declaration: <entity_id>:meta about sanic-routing

[ahopkins]

@hieulw Using : may not be a safe pattern since it is a reserved token in the RFC specification. Regardless, you can continue to use it as described in the docs for regex matching.

@app.get(r"/<entity_id:(?P<entity_id>.*)\:mode>")
async def handler(request: Request, entity_id):
    return json({"entity_id": entity_id})

Since your example only contains one matching group (the entity_id) you can simplify it:

@app.get(r"/<entity_id:(.*)\:mode>")

To have an exact parity with the str pattern:

@app.get(r"/<entity_id:([^/]+)\:mode>")

This final one is probably what you want.

I hope you fix the regex pattern to suit more cases.

I am not aware of any unsupported cases that do not meet the documentation. Happy to hear if there are others.

[ahopkins]

@hieulw Nothing we can't solve without a bit of regex magic 🪄

@app.get(r"/<entity_id:([^/]+)\:mode>")
async def handler_mode(request: Request, entity_id):
    return json({"entity_id": entity_id, "mode": True})


@app.get(r"/<entity_id:(?P<entity_id>[^/]+)(?!\:mode)>")
async def handler_reg(request: Request, entity_id):
    return json({"entity_id": entity_id, "mode": False})

$ curl localhost:9999/1234 localhost:9999/4567:mode
{"entity_id":"1234","mode":false}
{"entity_id":"4567","mode":true}

[hieulw]

I attempt to change the regex, but it will not recognize a route that contains colon :
How can I change this behavior ? : is really needed in my route, and It cannot change

[hieulw]

@app.get(r"/<entity_id:([^/]+)\:meta>")

Thanks @ahopkins! This approach works very well, but it seems /<entity_id> and /<entity_id:([^/]+)\:meta> are considered the same route, which not what I expected.