Jeremy Daly

Good catch. Looks like I'm just taking the attribute name and prefixing it with a `#`, but clearly that will cause issues. I should be able to switch it to...

Hi @ankitaabad! I know this is an old question, but can you post your Table and Entity configuration?

This was by design, but I suppose we could disable it with a flag. Adding to roadmap.

I was under the impression that v3 would have the same semantics as v2, just a different import method. If that's the case, I don't think any changes will be...

Yes, we discovered this right after v3 was released. Still looking for suggestions for handling this, but it would be really nice if AWS would reimplement the `DocumentClient`.

It’s either that, or we build the marshaling and unmarshalling into the platform.

Yup. The question is do we make that a dependency? We could do that and then require the user to pass in the v3 DynamoDB client like we do currently...

The issue with v3 is that there isn’t a `DocumentClient`, which is what this library uses under the hood. I’ve already built some prototypes that use v3 and apply `marshall`/`unmarshall`...

I'll need to check the compatibility with the library!

Yes, this is coming. We've been waiting on our migration to [v0.4](https://github.com/jeremydaly/dynamodb-toolbox/tree/v0.4) that does automatic type inferencing. This should be ready soon.