about the : in path param

[BiuXWT]

A url like this

/usr/:name/number/:id/do:work

the :work is not a param , the whole do:work string is a phrase ,
but now , the framework will consider work as a param,could you please fix it

[yhirose]

@BiuXWT thanks for the report!

[yhirose]

@bgs99 do you have any thoughts on this issue?

[bgs99]

@bgs99 do you have any thoughts on this issue?

I guess we could limit path parameters capture to whole path segments, so /:param would be a capture, but /not:param would be a literal segment with : in the middle.

It might break code for the users that already depend on capturing segment parts. But on the other hand, it seems that path parameter capture on segment parts is neither fully supported nor documented: it uses /: to select between named params capture and regex capture and only full segment capture is shown as examples in the docs.

Alternatively, if we want maximum flexibility, it should be possible to provide some kind of escaping mechanism, like writing /not\:param to mean /not:param literal.

[yhirose]

@bgs99 I like "limit path parameters capture to whole path segments". Could you take care of it and make a pull request, since I don't know much about the PathParamsMatcher code. Thanks!