Open fabiocav opened 7 years ago
Just ran into this on functions v2 framework core 2.2 when binding to a POCO from the query. It doesn't look like Enum binding is supported. Dredging up a super old issue here but are there any plans to at least expose some model binding extension points in the framework (similar to IModelBinder / Provider / IValueProvider etc.) for custom model binding like traditional dotnet core api has?
Any plans on ever supporting this? It doesn't seem to be working on querystring parameters either, which IMO is a pretty common use case.
Milestone unknown. Any update on this or other developments that would make this possible (like the model binding extension ports as mentioned before)?
Checking on this 6 years later. I wonder why Microsoft is pushing Azure functions (as pure REST APIs) so hard if simple things like this have been handled in Web API for years and years and years.
Currently, Enum binding is not supported from URI, so the following would not work:
Route: func/{myenum}
Function:
This should be supported.