Updating actor serialization documentation #1371
Merged
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.
Description
Updated the actor serialization documentation to reflect the differences between the JSON serialization and the Data Contract serialization approaches used in the Dapr.Actors SDK, how they relate to the different actor client types and some examples of how to properly use each of them.
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
This addresses a comment left at #1073 (comment) and occasionally seen in Discord though doesn't have an open issue that I see.
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list: