Skip to content

Conversation

msosnicki
Copy link
Contributor

Background

Proposal to loosen the enum and union openness requirement in the smithy spec


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@msosnicki msosnicki requested a review from a team as a code owner September 30, 2025 12:38
@msosnicki msosnicki requested a review from sugmanue September 30, 2025 12:38

## Abstract

In the Smithy 2.0 specification enums and unions are treated as strictly **open**: adding a member is always treated as a backward‑compatible change and clients are expected to handle unknown members at runtime. This RFC proposes to update the spec and loosen the strict requirements around open enums and unions, acknowledging the fact that for some use cases and protocols it may not be desireable. It will also align the spec closer to reality, as smithy4s do not follow the current spec.
Copy link
Contributor Author

@msosnicki msosnicki Sep 30, 2025

Choose a reason for hiding this comment

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

Currently the smithy-trait-codegen also do not follow the spec, see here

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.

1 participant