Skip to content

fix: criteria for event stream member detection #1624

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

Merged
merged 1 commit into from
Jun 20, 2025

Conversation

kuhe
Copy link
Contributor

@kuhe kuhe commented Jun 20, 2025

corrects the criteria from #1623

http payload trait is not required and the member itself will not have the streaming trait.

@kuhe kuhe requested a review from a team as a code owner June 20, 2025 01:40
@@ -454,7 +452,7 @@ private void generateEventStreamDeserializer(GenerationContext context, UnionSha
});
});
});
writer.write("return {$$unknown: output};");
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this fixes a bug introduced in #572

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

there's no impact because $unknown events are dropped from the asyncIterable

@kuhe kuhe force-pushed the fix/eventstream branch from 0efa79b to 6a7f3cf Compare June 20, 2025 01:44
@kuhe kuhe force-pushed the fix/eventstream branch from 6a7f3cf to 4e5602d Compare June 20, 2025 01:47
@kuhe kuhe merged commit 48f4e43 into smithy-lang:main Jun 20, 2025
11 checks passed
@kuhe kuhe deleted the fix/eventstream branch June 20, 2025 16:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants