The HttpTriggerOptions.route property needs better documentation

[anddoutoi]

Figuring out what patterns and syntax the route property supports is hard. Finding clear documentation is close to impossible.

• Customize the HTTP endpoint is far from satisfactory
• Route Constraints fill in some gaps but still leaves out for implicit interpretations

I think that a page like Express routing but for azure functions/static web apps API routing is needed.

[ejizba]

We got more feedback that this is confusing, so bumping priority a bit

https://github.com/MicrosoftDocs/azure-docs/issues/112725

Especially for model v4, it seems like you should be able to use route parameters like this:

app.http('httpTrigger1/{id}', {
    methods: ['GET', 'POST'],
    authLevel: 'anonymous',
    handler: httpTrigger1
});

But you have to do this:

app.http('httpTrigger1', {
    methods: ['GET', 'POST'],
    authLevel: 'anonymous',
    route: 'httpTrigger1/{id}',
    handler: httpTrigger1
});

[ejizba]

Between now and my last comment we added model v4 samples to the existing docs: https://learn.microsoft.com/en-us/azure/azure-functions/functions-bindings-http-webhook-trigger?tabs=python-v2%2Cin-process%2Cnodejs-v4%2Cfunctionsv2&pivots=programming-language-javascript#customize-the-http-endpoint

Further improvements will be tracked with:
#167