fix(dynamodb-seeder): Correct S3 file stream handling with transformToString #218
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.
Resolve the issue: #214
Summary
Fixes JSON parsing errors in the DynamoDB seeder by:
body.toString()
withtransformToString('utf-8')
for proper S3 stream handlingChanges
getSeedsFromS3
to use AWS SDK v3'stransformToString
:Impact
Unexpected token
errors when parsing seed filesError Context
Fixes cases where
body.toString()
corrupted S3 files, causing errors like:Unexpected token 'o' in JSON at position 1