dynamodb-toolbox icon indicating copy to clipboard operation
dynamodb-toolbox copied to clipboard

A simple set of tools for working with Amazon DynamoDB and the DocumentClient

Results 130 dynamodb-toolbox issues
Sort by recently updated
recently updated
newest added

Using the current `alpha` version (`0.4.0-alpha.2`), it seems that while type inference seems to work for checking the arguments passed to Entity.put, it doesn't work for giving the correct return...

bug

it will be nice to switch to the modularized AWS SDK for JavaScript v3 (https://github.com/aws/aws-sdk-js-v3) since it reached gamma status. AWS Amplify is already using it. dynamodb-toolbox doesn't require the...

question

Migrating from aws-sdk-js-v2 to aws-sdk-js-v3. (https://github.com/jeremydaly/dynamodb-toolbox/issues/155) It uses DynamoDB Document Client v3.

i get this error when trying to override the created/modified default values as shown in the readme to make mocking easier ``` attributes: { ... created: { default: () =>...

Similar to the `transform` function in `EntityAttributeConfig`, it would be super helpful for transforming data from DDB. Would be super helpful for cases like dates where they are stored as...

So I get a type error when trying to have a list of sub-objects on my primary object type. This is my setup. ```ts export interface MyObject { id: string...

Are there docs or examples around defining and querying nested attributes? I [see docs](https://github.com/jeremydaly/dynamodb-toolbox#update-nested-data-in-a-map) for updating nested attributes, but they don't include the entity definition. I also checked the [put...

Hello, When querying table with partitionKey and sortKey, I keep getting the following error ``` TypeError: Cannot read property 'type' of undefined at /node_modules/dynamodb-toolbox/dist/lib/validateTypes.js:17:21 at Table.queryParams (/node_modules/dynamodb-toolbox/dist/classes/Table.js:418:52) at Table. (/node_modules/dynamodb-toolbox/dist/classes/Table.js:254:75)...

It is not immediately clear that the default value is not a "request" default, but actually translates to `if_not_exists`. This should be improved in the documentation.

I'm new to this library and trying to model my data in line with https://www.alexdebrie.com/posts/dynamodb-one-to-many/. I describe my user ("main" entity) like this: ``` export const UserEntity = new Entity({...

enhancement