In current API route parameters must be part of both method's name and method's arguments list.
However this incurs on additional issue whenever the user has a mistake and puts a non matching name between arguments and method's name. In this case the connect-controller cannot detect if it is a typo or a deliberate intention of considering that argument as no route parameter, but instead a query-string.
So, to avoid this scenario we should follow the express convention for route paths definition and the user must define the property name as a string, to allow the use of / and : symbols. For simpler cases, without route parameters the user may still use the lower camel name corresponding to the route path.
Finally, remove support for methods defined with underscores.
In current API route parameters must be part of both method's name and method's arguments list.
However this incurs on additional issue whenever the user has a mistake and puts a non matching name between arguments and method's name. In this case the connect-controller cannot detect if it is a typo or a deliberate intention of considering that argument as no route parameter, but instead a query-string.
So, to avoid this scenario we should follow the express convention for route paths definition and the user must define the property name as a string, to allow the use of
/and:symbols. For simpler cases, without route parameters the user may still use the lower camel name corresponding to the route path.Finally, remove support for methods defined with underscores.