airframe-http: Allow more flexible http path routing

[takezoe]

The current implementation of airframe-http's router allows to define the parameter only at the last component of the path. This pull request allows more flexible http path routing like:

• /:param/hoge
• /:param1/hoge/:param2

See also #417

[codecov]

Codecov Report

Merging #418 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #418      +/-   ##
==========================================
+ Coverage   82.41%   82.42%   +<.01%     
==========================================
  Files         165      165              
  Lines        6068     6071       +3     
  Branches      607      609       +2     
==========================================
+ Hits         5001     5004       +3     
  Misses       1067     1067

Impacted Files	Coverage Δ
...tp/src/main/scala/wvlet/airframe/http/Router.scala	97.43% <100%> (+0.21%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 71cea45...ed1b9ab. Read the comment docs.

[xerial]

Thanks for the fix!

[takezoe]

Thanks for merging.

Remaining concern is that it's unclear which endpoint is called if multiple endpoints are matched with the request path. We might have to improve the path matching logic to have the clear and stable behavior for conflicting path definitions.

For example, it might be better to give priority to the concrete path definitions (e.g. /user/info) than the parameterized path definitions (e.g. /:id/info). Currently, it depends on the order of definition of methods.

[xerial]

I think we should run some conflicting path check when creating Route instances.