Closed daniloraisi closed 1 month ago
Customers should be using the supported Azure Functions language workers for those languages, not custom handlers. We found that having them here led to confusions.
I understand, but there are edge cases on Node, for example, that custom handlers saves a lot of time and work.
Can you share what these edge cases are? Would like to address them in the Node worker if possible.
Customers should be using the supported Azure Functions language workers for those languages, not custom handlers.
@anthonychu Then C# with .NET 5.0 supported?
Could someone from the team elaborate on why they were removed? For Java, for instance, using a custom handler means:
...why wouldn't I want that?
@anthonychu for Node, there is one edge case that I can share. If I have a big legacy project in Express.js with lots of endpoints and I want to deploy it to Azure Functions without rearchitecting my code, then Custom Handler can do the job.
Why did code samples for C#, Java, and Node were deleted by Pull Request #12?