Throw type error if data is not string

[dlhandsome]

The result would be the same if data is not a string when we want to get a hashcode.

For example:

const Crypto = require('crypto-js');

console.log(Crypto.MD5(1).toString()) // 487f7b22f68312d2c1bbc93b1aea445b
console.log(Crypto.MD5(2).toString()) // 487f7b22f68312d2c1bbc93b1aea445b
console.log(Crypto.MD5(3).toString()) // 487f7b22f68312d2c1bbc93b1aea445b
console.log(Crypto.MD5([32, 0, 0, 0]).toString()) // 487f7b22f68312d2c1bbc93b1aea445b

So, we should throw type error under these circumstances.

[dlhandsome]

#203

[Alanscut]

Looks Good 👍

[majorhayes]

Wouldn't this mean that you can't pass a WordArray object in anymore? Why would you want to remove that feature?

[evanvosberg]

Wouldn't this mean that you can't pass a WordArray object in anymore? Why would you want to remove that feature?

Adding type check is fine, but this should not remove the possibility to use WordArray beside String.