Lukas Siemon

Results 86 comments of Lukas Siemon

Figure out the story for onlySpecified in npm@3

I'd also very much love to have this option.

Query and Scan do not parse `sets`.

What is the status on this?

Query and Scan do not parse `sets`.

Any update on this?

Query and Scan do not parse `sets`.

:wave:

Query and Scan do not parse `sets`.

ping

Query and Scan do not parse `sets`.

👋

Query and Scan do not parse `sets`.

Looks like this is not working as expected. We are trying to add [entity](https://github.com/jeremydaly/dynamodb-toolbox/blob/3e7cda83fe766722c9b5dac20a5f1ab888ab1c2e/docs/docs/table/methods.md#scan) into `scan` and `query`, but it doesn't seem to fix the issue. > `entity`: The name...

Query and Scan do not parse `sets`.

For reference, this doesn't work: https://github.com/blackflux/aws-sdk-wrap/pull/2151/files We'll try and get a minimal test case in so it's easier to reason about. Don't have an eta for that though

Query and Scan do not parse `sets`.

> At the moment what you can do is add the entity name (_et by default) field with the entity name and it would be parsed properly, just make sure...

Query and Scan do not parse `sets`.

FYI Yes, we did disable that since we only have one entity type per table.