Nested attributes Incompatibility for v1.0.1

[dlackty]

We're recently migrating our zapier-ruby to latest version and found some webhooks broken.

For zaps using nested attributes (e.g. { foo: { bar: buz } }), it turned out the previous version (with rest-client) will becomes foo[bar] and new version (with native Ruby HTTP lib) will become foo__bar.

I checked the Zapier documentation, and it looks like the new behavior is expected.

Instead of trying to restore the old behavior, I suggest adding some notices on README. What do you think?

[pete2786]

Sounds good, could you suggest what might be most helpful to folks?

[dlackty]

Probably like this:

Important breaking change for nested attributes in 1.0.1

Due to an internal change, we fixed the wrong behavior of nested attributes in webhook but it also breaks your existing zaps integrating with previous version of zapier_ruby.

To fix, you need to change any nested references from foo[bar] to foo__bar.

See Zapier documentation for further details on how they treat nestled attributes.