Azure-docs: This sample is not fit to explain function chaining
I think HelloSequence sample is not good to explain function chaining.
Document Details
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
- ID: 3b6ce511-60d0-9d1a-cf6f-c955adeae20b
- Version Independent ID: 0da09c8f-0a2f-26e4-2948-fcb43f67e251
- Content: Function chaining in Durable Functions - Azure
- Content Source: articles/azure-functions/durable-functions-sequence.md
- Service: azure-functions
- GitHub Login: @cgillum
- Microsoft Alias: azfuncdf
options
All 3 comments
@options What do you think would be a better example to use?
cgillum
on 16 Sep 2018
👍1
Regarding the first lines of this doc, where it states, that often output of one function is the input of the next and so on..., I would suggest, to take an example, that builds up a string (e.g. Start "" -> Func1 >> "The" -> Func2 >> "The big" -> Func3 >> "The big green" -> Func4 >> "The big green apple." -> End) This is not that optimal example, but it demonstrates the core of the topic.
totosan
on 17 Sep 2018
👍3
That's fair feedback. We'll look into updating this sample.
cgillum
on 17 Sep 2018
Was this page helpful?
0 / 5 - 0 ratings
Related issues
varma31
·
3Comments
bdcoder2
·
3Comments
jharbieh
·
3Comments
jamesgallagher-ie
·
3Comments
Favna
·
3Comments
Most helpful comment
Regarding the first lines of this doc, where it states, that often output of one function is the input of the next and so on..., I would suggest, to take an example, that builds up a string (e.g. Start "" -> Func1 >> "The" -> Func2 >> "The big" -> Func3 >> "The big green" -> Func4 >> "The big green apple." -> End) This is not that optimal example, but it demonstrates the core of the topic.