-
Notifications
You must be signed in to change notification settings - Fork 640
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DynamoDB Expression Package #981
Merged
Merged
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
skmcgrail
force-pushed
the
ddbExpression
branch
from
December 16, 2020 03:16
0c0d608
to
a9025cc
Compare
jasdel
approved these changes
Dec 16, 2020
skmcgrail
force-pushed
the
ddbExpression
branch
2 times, most recently
from
December 17, 2020 01:18
e57dc13
to
3173800
Compare
skmcgrail
force-pushed
the
ddbExpression
branch
from
December 17, 2020 01:21
3173800
to
c2286fd
Compare
@skmcgrail was there a reason for not including |
zaquestion
pushed a commit
to zaquestion/aws-sdk-go-v2
that referenced
this pull request
Jul 1, 2021
skmcgrail
added a commit
that referenced
this pull request
Jul 21, 2021
* feat: (feature/dynamodb/expression) readd IsSet methods These changes were present in an older version of the expression package before it was moved, originally added in #494, when the expression library was reintroduce in #981 these changes werent included for some reason, but the need for checking if a condition is set or not still exists * Add Change Annotation Co-authored-by: Sean McGrail <mcgrails@amazon.com>
jrichard8
pushed a commit
to jrichard8/aws-sdk-go-v2
that referenced
this pull request
Feb 14, 2022
* feat: (feature/dynamodb/expression) readd IsSet methods These changes were present in an older version of the expression package before it was moved, originally added in aws#494, when the expression library was reintroduce in aws#981 these changes werent included for some reason, but the need for checking if a condition is set or not still exists * Add Change Annotation Co-authored-by: Sean McGrail <mcgrails@amazon.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR re-introduces the
feature/dynamodb/expression
package.Currently this branch is based on #975 thus the diff includes those changes. Will rebase this PR after that is merged in. For now leaving this as a draft.
Fixes: #894
Fixes: #713
Related: #115