New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The functionName query parameter is always "raw" member name vs "logical name" supplied by FunctionNameAttribute #14

drub0y opened this Issue Sep 12, 2017 · 1 comment


None yet
1 participant

drub0y commented Sep 12, 2017

Because of this line of code:

return Task.FromResult<ITriggerBinding>(new EventGridTriggerBinding(context.Parameter, _extensionConfigProvider, context.Parameter.Member.Name));

The functionName querystring parameter for the web hook will always be the "raw" member name of the .NET class rather than the "logical name" that might be assigned by the FunctionNameAttribute.

I'm not sure how big of an issue this ultimately is, but as I was testing locally I expected to put the logical name (like you would for an HTTP triggered function) and it wasn't working and that's how I found this bug.


This comment has been minimized.

Show comment
Hide comment

drub0y Jan 25, 2018

I believe this is fixed by #19 as well.

drub0y commented Jan 25, 2018

I believe this is fixed by #19 as well.

@drub0y drub0y closed this Jan 25, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment