Fixed bug in VersionedRecord that did not allow special characters in… #3282
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.
… version key name, github issues #2507, #2950, #3279
Motivation and Context
The VersionedRecordExtension makes use of the VersionedRecord tag/annotation, letting users auto-increment versions of their records. However the extension does not use ExpressionNames in its conditions/expressions, only ExpressionValues. Therefore, if your record has a version attribute with reserved words or special characters, DDB put/update item calls will fail.
Modifications
Testing
All tests pass
Screenshots (if appropriate)
Types of changes
Checklist
mvn install
succeedsscripts/new-change
script and following the instructions. Commit the new file created by the script in.changes/next-release
with your changes.License