Convention-based FunctionName & HttpTrigger Routes #257
To enable MVC-like conventions within functions, I wish:
there was a parameter-less version of the FunctionNameAttribute that would default the name to:
the HttpTriggerAttribute Route property was optional and would default to:
The goal would be so that these two would produce the same result.
Note: I think the snippets above might need more logic. For example, I'd prefer to not include the first namespace if there is more than one (eg: "Service" from the screenshot above). The first namespace is often just the solution name or something that you don't necessarily want reflected in the route.
I realize that FunctionNameAttribute can't call
Anyway, edit 2 on this SO post describes a method for obtain details on the calling class that might enable convention-based naming for functions.