Repository navigation
fix(parser): accept non-string DynamoDB tumbling window state - #6001
Merged
dreamorosi merged 2 commits intoNov 18, 2026
Merged
dreamorosi merged 2 commits into
dreamorosi merged 2 commits into
Conversation
dreamorosi
approved these changes
Nov 18, 2026
dreamorosi
left a comment
Contributor
There was a problem hiding this comment.
Thank you for fixing this!
dreamorosi
enabled auto-merge (squash)
November 18, 2026 15:12
This file contains hidden or 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
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.
Summary
DynamoDBStreamSchemaonly accepted strings in the tumbling windowstate, but Lambda passes back whatever state the function returned, and the Lambda docs use numbers there. The schema now accepts any value, the same asKinesisDataStreamSchema.Changes
stateinDynamoDBStreamSchemais nowz.record(z.string(), z.unknown()), so the inferredDynamoDBStreamEvent['state']type changes fromRecord<string, string>toRecord<string, unknown>.mainwithInvalid input: expected string, received numberand passes with this change.npm run test:unit:coverage,npm run lint,npm run build:testsandnpm run test:unit:typespass inpackages/parser, and coverage stays at 100%.Issue number: closes #5999
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.