Enforce constraints for unnamed enums #3884
Draft
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.
Enforces Constraints for Unnamed Enums
This PR addresses the issue where unnamed enums were incorrectly treated as infallible during deserialization, allowing any string value to be converted without validation. The solution introduces a
ConstraintViolation
andTryFrom
implementation for unnamed enums, ensuring that deserialized values conform to the enum variants defined in the Smithy model.This change prevents invalid values from being deserialized into unnamed enums and raises appropriate constraint violations when necessary.
Fixes issue #3880