-
Notifications
You must be signed in to change notification settings - Fork 196
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
missing RuntimeConfig
node should behave the same as {}
#1678
Conversation
A new generated diff is ready to view.
A new doc preview is ready to view. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Will be interesting to see if this breaks the SDK CI or not--we probably don't explicitly set a path dependency for it.
codegen/src/main/kotlin/software/amazon/smithy/rust/codegen/smithy/RuntimeTypes.kt
Outdated
Show resolved
Hide resolved
RuntimeConfig
node should behave the same as {}
Co-authored-by: John DiSanti <[email protected]>
A new generated diff is ready to view.
A new doc preview is ready to view. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you.
A new generated diff is ready to view.
A new doc preview is ready to view. |
Motivation and Context
Address #1676. #1635 forgot to handle a case that the whole
RuntimeConfig
is missing.Description
If seeing a empty node for where
RuntimeConfig
should be, we just treat it as{}
empty object. They now share the same behaviour that by default using runtime crates with the versions from crates.io.Testing
Checklist
CHANGELOG.next.toml
if I made changes to the smithy-rs codegen or runtime cratesCHANGELOG.next.toml
if I made changes to the AWS SDK, generated SDK code, or SDK runtime cratesBy submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.