Azure / Azure/azure-functions-dotnet-worker
Catch ambiguous match exceptions at build
Open
supportability: analyzer
team-issue
- Dominant language
- C#
- Stars
- 466
- Forks
- 215
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 7
Description
If you happen to have two `Run` methods in your application with the same namespace and class -- you'll end up with an ambiguous match exception when the worker attempts to find the method to call. This should be something we can validate at build time to prevent this -- if any two functions have the same Assembly and EntryPoint, they'll be ambiguous matches at runtime.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.