Correcting .NET examples in the workflow docs #4627
+3
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thank you for helping make the Dapr documentation better!
Please follow this checklist before submitting:
In addition, please fill out the following to help reviewers understand this pull request:
Description
Following in the steps of past PRs, I'm submitting a few tiny changes to the .NET examples in the workflow documentation that should be corrected for greater clarity and to put forward ideas of how things should be done in the "real world". My hope is that by being clear about this in the examples, we can avoid assuming that developers would "just know" that toy examples aren't actually following best practices and teach them from example how to properly do everything from the get-go.
Issue reference