bulk-cdk-toolkit-extract-cdc: fix default value handling in PartialConverter #49970
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
rodireich
approved these changes
Dec 20, 2024
postamar
force-pushed
the
postamar/bulk-cdk-fix-default-value-handling-in-partial-converter
branch
from
599d3b7 to
4acc4a2
Compare
postamar
deleted the
postamar/bulk-cdk-fix-default-value-handling-in-partial-converter
branch
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.
What
Fixes a bug related to default value handling in the CustomConverter tooling added in #49923
I stumbled upon this when adding default value test cases in #49918
How
Default values also need to be converted!
Review guide
n/a
User Impact
None
Can this PR be safely reverted and rolled back?