Don't duplicate PartitionKey/RowKey properties in storage #27
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Switch to expressions for table repository, so we can inspect the lambda looking for the actual property name being used for partition/row keys. This way we can avoid persisting those as (duplicate) individual columns (since they will already be persisted as partition/row keys). For document-based storage, we don't need to distinguish, since we persist the entire serialized object, so it's not useful in that case to try to avoid persisting them separately. Fixes #26
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Switch to expressions for table repository, so we can inspect the lambda looking for the actual property name being used for partition/row keys. This way we can avoid persisting those as (duplicate) individual columns (since they will already be persisted as partition/row keys).
For document-based storage, we don't need to distinguish, since we persist the entire serialized object, so it's not useful in that case to try to avoid persisting them separately.
Fixes #26