Add options hash / Add lower casing of key names

[hacklschorsch]

I want to integrate your parser into the NodeJS 'node-imagemagick' module (https://npmjs.org/package/imagemagick) because the parser in that module won't digest bogon input (as I receive it from graphics magick for a couple of test images) and is not very legible.

node-imagemagick likes to have the keys of the parsed Identify output lowercased, and the IMHO best way is to add that feature to your module.

I have added a unit test.
I have not added a test for combining lowerCase=true with camelCase=true, though it is possible to do.

[dandean]

Hello! Thanks for the patch. If this module is to perform different and mutually exclusive transforms, I'd prefer to not use an options object. Would you mind refactoring into something like this:

/**
 * ImageMagickIdentifyReader(text[, transform]) -> ImageMagickIdentifyReader
 * - text (String): Output text from the `identify` program.
 * - transform (String): Optional key transformation: "camel" | "lower"
 *
 * Returns a parsed object representation of the input string.
 *
 * The optional `transform` argument can instruct this module to transform keys
 * into different formats: "camel" converts keys to camelCase and "lower" to
 * lower case. For backwards compatibility, the Boolean value `true` will be
 * treated as "camel".
**/

If you're cool with this, I'll gladly merge it in.

[hacklschorsch]

Hi Dan!

I don't mind at all. I like option hashes for they allow easy extending later without breaking backwards compatibility. Also, the 'lowerCase' and 'camelCase' are not exclusive, they can be combined (don't know if it makes much sense though). May I propose packing the 'transform': directive into an options hash, so the next crazy feature won't have to change the API in a breaking way again?

Never the less, I'll post the change ASAP. Glad you had the time to look at my patch so quickly!

[hacklschorsch]

Also, previously, not only "the Boolean value true" (was) "treated as camel" but instead all "tru-ish" values. I'll try to respect that in my patch.

[hacklschorsch]

What do you think of the patch?