Fabio Cavalcante
Fabio Cavalcante
@NickCraver odd, I don't see the usual list, just the conflict warning in GH. If you can merge locally, go for it!
Marking as blocked by work from @vrdmr's team that is currently in progress. Will pick this back up when we can move forward.
This is being iterated on. Currently in PR.
Keeping this in 131. @arroyc can you please assist so we can close on this item?
This is consistent with the behavior you'd see in a standard ASP.NET Core application. The response would end up being treated as an ObjectResult and serialization would be attempted there....
@alrod @AnatoliB is this still relevant? Are you tracking this elsewhere?
+ @pragnagopa
@amamounelsayed @VpOfEngineering this is something that is missing after our move from AppVeyor. Happy to sync on this if it helps.
This is possibly a language worker conversion issue. Needs investigation to determine the problem
This is interesting! For triggers, we could potentially expose this as binding data. For the input/output bindings, would emitting a log with that information be helpful?