You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This caused us a great headache, because we only could detect it after deploying to Azure. Since 1.0.31 something changed, that when you declare your durable activity functions inside nested classes like this:
publicclasssomeFunction{[FunctionName("someFunction")]publicasyncTask<List<string>>RunOrchestrator([OrchestrationTrigger]IDurableOrchestrationContextcontext){varoutputs=newList<string>();// Replace "hello" with the name of your Durable Activity Function.
outputs.Add(await context.CallActivityAsync<string>("someFunction_Hello","Tokyo"));
outputs.Add(await context.CallActivityAsync<string>("someFunction_Hello","Seattle"));
outputs.Add(await context.CallActivityAsync<string>("someFunction_Hello","London"));// returns ["Hello Tokyo!", "Hello Seattle!", "Hello London!"]returnoutputs;}publicclassActivities{[FunctionName("someFunction_Hello")]publicstringSayHello([ActivityTrigger]stringname,ILoggerlog){
log.LogInformation($"Saying hello to {name}.");return$"Hello {name}!";}}}
The function.json for the nested function, someFunction_Hello, is totally missing from the ouput since SDK 1.0.31. This is the output of SDK 1.0.31 build:
We tried this on SDK versions 1.0.33 and 1.0.34 with the same wrong output. We hope we don't need to change our coding conventions because of this and the team can fix it.
The text was updated successfully, but these errors were encountered:
This caused us a great headache, because we only could detect it after deploying to Azure. Since 1.0.31 something changed, that when you declare your durable activity functions inside nested classes like this:
The function.json for the nested function,
someFunction_Hello
, is totally missing from the ouput since SDK 1.0.31. This is the output of SDK 1.0.31 build:While SDK 1.0.29 does generate someFunctionHello's function.json, generating a correct output:
We tried this on SDK versions 1.0.33 and 1.0.34 with the same wrong output. We hope we don't need to change our coding conventions because of this and the team can fix it.
The text was updated successfully, but these errors were encountered: