Normalise Scan response shape when using "RawAWSFilter" #320
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.
Problem
When using a raw AWS filter to Scan the returned Item shape is not consistent with a regular Scan.
Instead of:
We get:
This is happening because
AWS.DynamoDB.DocumentClient
createsSet
instances for attributes of type StringSet etc. These aren't native instances ofSet
but rather a custom AWS Class which isn't exposed.Solution
When mapping over the returned objects within
Scan.js
I iterate over each items properties and check for such instances to convert them to regular array instances.