fix(const-to-enum): handle boolean schema in properties#1845
Merged
cdklabs-automation merged 1 commit intomainfrom Jan 6, 2026
Merged
fix(const-to-enum): handle boolean schema in properties#1845cdklabs-automation merged 1 commit intomainfrom
cdklabs-automation merged 1 commit intomainfrom
Conversation
iliapolo
approved these changes
Jan 6, 2026
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.
JSON Schema allows
trueas a shorthand for an empty schema that accepts any value. TheconstToEnumtransformer was failing when encountering such boolean schemas in properties because thehasConsttype guard assumed the input was always an object.This adds a type check to handle boolean schemas gracefully, preventing runtime errors during transformation.
Ask Yourself