Fix typo (Dynanmo->Dynamo).

[pkulev]

• Fixed typo in DynamoDB exception class name.
• Fixed tests.
• Provided alias for backward compatibility.

[jamesls]

We should definitely get this fixed. Only question is whether it's worth aliasing the typo'd exception for backwards compatibility. I could go either way on that second point.

@kyleknap - thoughts?

[rayluo]

For that second point, the fancy way is to provide aliases for backwards compatibility, AND also mention they are deprecated in the release note, and then a couple versions later we will get rid of them.

That being said, in this case the previous behavior can be considered as a bug, and a bug is always fixed without "backward compatibility".

[pkulev]

Ok, guys, I added alias.
But IMHO this is not such case when there's a need to provide aliases.
This is bug, not sort of deprecated thing.

[jamesls]

Looks good to me.

[kyleknap]

@jamesls
The error is there for validation purposes. It tells you that the condition you tried to use cannot be used. I am having trouble imagining someone trying to catch this exception specifically because you really cannot do anything with the error or have logic that relies on that error being thrown because you have to physically fix your condition statement in order to even be able to make a successful call.

However, I suppose if you are building an application on top of the dynamodb library, and you wanted to modify the message sent back for these validations to the user that would break the application. As much as I really do not like that spelling mistake in there it is the right thing to alias it for backwards compatibility and deprecate it (since it is a bug/mistake) as @rayluo mentioned, and which I noticed @pankshok you already made.

Thanks for the catch. Merging.