Mario Izquierdo

Thank you. Could you elaborate why this option would be useful? We would also need tests to cover the new use-case. I can review the docs and code comments after...

linking a related issue to use `ActiveSupport::Notifications.instrument` that would also have benefited from an `around { ... }` hook: #49

What do you think of this design? ```rb svc = Example::HelloWorldService.new(handler) svc.before do |rack_env, env| env[:beforefoo] = "bar" end svc.around do |s, env| puts env[:beforefoo] # before hooks were called...

also, a link to the usage guide would be great `:)` https://github.com/github-for-unity/Unity/blob/master/docs/using/quick-guide.md

I don't have plans to support such a feature. `jquery.serializeJSON` is built on top of [jquery.serializeArray](http://api.jquery.com/serializearray/), which is one of the reasons why the code is so stable. The `.serializeArray()`...

Yes, the confusion with the checkboxes is actually pretty common. I blame the W3C standard ;)

@endeavor85 I was thinking a little more about how common is the checkbox problem and I came up with a solution that is not obtrusive. By default, `serializeJSON` still does...

It's true I wrote the "why it's better" a while ago and certain checks don't really differentiate `serializeJSON` anymore. I just updated the README file with more accurate info in...

It seems you expect the plugin to handle a different syntax. This plugin works with the syntax `key[nested][nested]`. Instead of key.nested.nested: ``` name="foo.bar.[0].prop" ``` This plugin uses key[nested][nested]: ``` name="foo[bar][0][prop]"...

How it can be updated to be used with jQuery 1.4 ?