feat(lib-dynamodb): large number handling

[kuhe]

Issue

fixes #5363

Description

This PR introduces an input side container for large/precise numbers not representable by the Native JS number type.

  const dynamodb = new DynamoDB({ region: "us-west-2", maxAttempts: 10 });
  const doc = DynamoDBDocument.from(dynamodb, {
    unmarshallOptions: {
      wrapNumbers: true,
    },
  });

To write a large or precise number:

import { DynamoDB } from "@aws-sdk/client-dynamodb";
import { NumberValue, DynamoDBDocument } from "@aws-sdk/lib-dynamodb";

// note, the client will not validate the acceptability of the number.
// it is only to preserve its precise representation.
DynamoDBDocument.from(new DynamoDB({})).put({
  Item: {
    id: NumberValue.from("1000000000000000000000.000000000001")
  }
});

(You can also use this wrapper for small numbers, but that is optional).
e.g.

new Set([
  1, "1234567890", 2, 3, 4
].map(NumberValue.from));

To read large or precise numbers, set

    unmarshallOptions: {
      wrapNumbers: true,
    },

as shown above. All numbers will be returned in the NumberValue wrapper.

Testing

new unit and e2e tests

Checklist

• update lib-dynamodb documentation
• If you wrote E2E tests, are they resilient to concurrent I/O?
• If adding new public functions, did you add the @public tag and enable doc generation on the package?

[github-actions]

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.