Closed wuhkuh closed 1 month ago
dev note: likely due to interaction between the all-optional args generating an additional no-arg method signature and the type transform only seeing the first available signature
a fix has been applied as of this version: https://www.npmjs.com/package/@aws-sdk/client-cloudformation/v/3.575.0, using ^3.0.0
of @smithy/types
.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.
Checkboxes for prior research
Describe the bug
When I'm casting a
CloudFormation
instance as one (or more) Smithy types (NodeJsClient
,AssertiveClient
, ...), it loses the type information.Update: Apparently this has a wider scope than just the method I'm interested in.
SDK version number
@aws-sdk/client-cloudformation@3.569.0 @smithy/types@2.12.0
Which JavaScript Runtime is this issue in?
Node.js
Details of the browser/Node.js/ReactNative version
v20.12.2
Reproduction Steps
Observed Behavior
You will see the following TypeScript error:
Expected Behavior
No type errors, like other method calls for the constructed client.
Possible Solution
No response
Additional Information/Context
It's incredibly hard to step through the generated types. It's definitely a problem related to Smithy code generation.