Function Names in the Wild
Whenever I see examples or implementations of Azure Functions I always see this:
Where the function name is present as a direct string literal. I’m not questioning that it is a string because that’s simply the way the
FunctionName attribute works currently. I’m more concerned how the string got there.
I’d like to show two ways to refer to function names in a safe and consistent way. This is especially useful when you’re using Durable Functions and need to refer to activity function names in your orchestration function.