Chris Howie

It fails because `test[0].title` is equal to `'hello1'`, not `'hello2'`. Use `.attributes()` to limit the attributes that are fetched from the database. See the [query documentation](https://github.com/clarkie/dynogels#query).

@clarkie Reading [this section](https://github.com/clarkie/dynogels/blob/master/lib/expressions.js#L135) of the code, it seems like we don't correctly handle array access expressions. As in the above example, `"test[0].title"` would be built as the equivalent of...

> `await MyModel.destroyAsync('Id-123', 'Id-123', { expected: { Id: { Exists: true } } })` > > generates > > ``` > Key: { Id: 'Id-123', EntityId: 'Id-123' }, > ExpressionAttributeNames:...

I agree that natively supporting promises would be nice. I'd suggest instead that the configuration parameter be a promise factory. By default it would be `global.Promise` but could be replaced...

I think it makes more sense to have the callback argument be optional. If not provided, asynchronous methods will return a promise instead.

I don't consider additional warnings to break backwards compatibility, as the program will function the same way in every other respect. In fact, the warnings could be very useful in...

@dangerginger No, this does not transform the key actually stored in the database. It affects the [alias](http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Expressions.ExpressionAttributeNames.html) that is used to reference a key in a projection/query expression. Basically, it...

@C45tr0 I left a code comment above pointing out a possible cleaned key collision scenario.

I can merge it but I'm not sure what good it would do; @clarkie doesn't seem to be around anymore and I don't have the ability to push releases to...

I would suggest that you continue to try to get the issue to show up in a test. We can't easily debug something that isn't reproducible.