clarkie/dynogels

using reserved word in schema causes silent error

Opened this issue · 0 comments

I tried to use "name" as a property in my schema (stupid mistake, I now know). The createTables() call failed, but it didn't report an error. Using a debugger took me down a rabbit hole. I'm sure the failure was deep inside the AWS SDK, but if dynogels could catch it, it could save hours of wasted time.

The list of reserved words (https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ReservedWords.html) is very long, so it would be pretty easy to make this mistake.