You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The change made in commit cb4a0e3 incorrectly reorders the overload that returns AttributeValue[] type instead of Record<string, AttributeValue> when passing in a JavaScript object to be marshalled.
SDK version number
@aws-sdk/util-dynamodb@3.363.0
Which JavaScript Runtime is this issue in?
Node.js
Details of the browser/Node.js/ReactNative version
The code above assigns ExpressionAttributeValues a type of AttributeValue[].
Expected Behavior
ExpressionAttributeValues should be assigned a type of Record<string, AttributeValue>.
Possible Solution
Swap the two overload signatures so that the one returning Record<string, AttributeValue> takes precedence. Otherwise this breaks a lot of existing implementations.
Additional Information/Context
No response
The text was updated successfully, but these errors were encountered:
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
The change made in commit cb4a0e3 incorrectly reorders the overload that returns
AttributeValue[]
type instead ofRecord<string, AttributeValue>
when passing in a JavaScript object to be marshalled.SDK version number
@aws-sdk/util-dynamodb@3.363.0
Which JavaScript Runtime is this issue in?
Node.js
Details of the browser/Node.js/ReactNative version
v18.15.0
Reproduction Steps
Observed Behavior
The code above assigns
ExpressionAttributeValues
a type ofAttributeValue[]
.Expected Behavior
ExpressionAttributeValues
should be assigned a type ofRecord<string, AttributeValue>
.Possible Solution
Swap the two overload signatures so that the one returning
Record<string, AttributeValue>
takes precedence. Otherwise this breaks a lot of existing implementations.Additional Information/Context
No response
The text was updated successfully, but these errors were encountered: