Fabio Cavalcante
Fabio Cavalcante
@brandonh-msft the serialization is not the main issue, the binding support is. A large number of apps use `JObject` as the binding target type. Removing that in the 3.0 timeframe...
@stevo-knievo the model with the OOP worker for .NET 5 in functions is a bit different, but you have full control over the stack there.
This is a documented limitation of the trigger, but it would be nice if the message was a little more helpful and stated the problem. Will flag this for follow...
@liliankasem can we please add information about the expected vs actual behavior here so others know how to validate this issue? Thanks!
@AdamCoulterOz, we'd be happy to help if you want to get a PR in, but we need to coordinate on documentation and host schema updates, in addition to the changes.
@CasperWSchmidt this is still the case. The activation/deserialization still require a default constructor and public setters for the POCO.
@MikeChristensen apologies for the delayed response here, but you're correct in your last comment. This is something that was introduced with a very narrow scope to support internal requirements and...
This work would likely happen after V2 GAs, but this would be a great feature. /cc @jeffhollan
One thing to note here is that the sum of timeout and grace period cannot exceed the maximum timeout for the SKU (e.g., 10 mins on Consumption Plans)
@mathewc FYI