Jest matchers don't allow use of jest submatchers for input object filtering

Checklist

• I have read Caveats documentation and didn’t find a solution for this problem there.

Bug description

The Jest matchers added here still use the sinon call matching logic here so jest submatchers don’t work. For example, I would expect this code to work:

expect(mock).toHaveReceivedCommandWith(QueryCommand, {
    TableName: expect.stringMatching(/^foo/)
});

Instead I get the following error:

Error: Expected DynamoDBDocumentClient to receive "QueryCommand" with {"TableName": StringMatching /^foo-/}
DynamoDBDocumentClient received "QueryCommand" 0 times
Calls:

  1. QueryCommand: {"ExpressionAttributeValues": {":guid": "guid"}, "KeyConditionExpression": "id = :guid", "Limit": 1, "ScanIndexForward": false, "TableName": "foo-undefined"}

Environment

• Node version: 14.19.3
• Testing lib and version: Jest
• Typescript version: 4.2.4
• AWS SDK v3 Client mock version: 1.0.0
• AWS JS SDK libs and versions:
  • @aws-sdk/client-dynamodb: 3.49.0
  • @aws-sdk/lib-dynamodb: 3.49.0

[m-radzikowski]

Thank you, I will check what’s the standard way of achieving this with custom Jest matchers and make an update.

[m-radzikowski]

#101