Allow arbitrary HTTP method types to be added as routes#2237
Allow arbitrary HTTP method types to be added as routes#2237aldas merged 1 commit intolabstack:masterfrom
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2237 +/- ##
==========================================
+ Coverage 92.34% 92.46% +0.12%
==========================================
Files 37 37
Lines 3123 3134 +11
==========================================
+ Hits 2884 2898 +14
+ Misses 150 145 -5
- Partials 89 91 +2
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
8f160b2 to
8742207
Compare
|
@lammel could you review this PR? |
|
bump @lammel , if you are on summer vacation do not reply :) I'll merge this today and bump a new release. |
lammel
left a comment
There was a problem hiding this comment.
Pure code review LGTM.
This means we really support any aribtrary HTTP method, even those not known of defined in any standard.
Should we limit the methods to a list of supported additional methods (like those specified for WebDAV)?
|
To me, it does not make sense or reason to limit it - if you want to support some proprietary method in your app then go ahead. |
Allow arbitrary HTTP method types to be added as routes.
This does not affect routing "usual" use-case performance as these arbitrary HTTP method types and underlying map is accessed only when request is of that type. This code is taken from
v5.Relates to;
Example:
Output: