Context expressions - Add support for Scan and Query using LINQ #3872
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.
This pull request introduces native support for LINQ expression trees in the IDynamoDBContext API for ScanAsync() and QueryAsync().
Description
Implement support to automatically translate LINQ expression trees to DynamoDB Expression
Example translation:
u => u.Age > 21 && u.Status == "Active"
becomes a ExpressionStatement like: #C0 > :C0 AND #C1 = :C1
with appropriate ExpressionAttributeNames and ExpressionAttributeValues.
ContextExpression
that will be used to define filter LINQ expressions as follows:Add in LinqDdbExtensions methods to be used inside expression trees to generate DynamoDB Expression functions as follows:
Extend
IDynamoDBContext
with a new overloads for Scan API:QueryConfig
to allow settingExpressionFilter
asContextExpression
.Motivation and Context
Testing
unit and integration tests added

benchmarking between filters methods and LINQ expression tree ones
Screenshots (if appropriate)
Types of changes
Checklist
License