Jens Ljungblad

Also interested in this! Any updates?

I've also noticed that the startup event is no longer working. Perhaps the same issue?

Oops, that was a typo from my end. Now the question should be corrected. The problem persists. We're looking into if the `for_template` option gets lost along the way somehow.

It works with the following changes: ``` ruby form_for @resource do |f| f.nested_fields_for :foo do |ff| ff.fields_for :bar do |fff| fff.nested_fields_for :baz, for_template: true do |ffff| # stuff end end...

Actually, if you set `for_template` on `fields_for` instead, it will pass it along and things seem to work. So no change needed? ``` ruby form_for @resource do |f| f.nested_fields_for :foo...

Yeah it would be great if everything could be configured at the wrapper level. Would also be nice if there were mentions in the README on how to do it....

Also got confused by this. Actually did try pasting but wasn't in select mode. Adding a button just for discoverability would be nice 👍

@brandur I was wondering what the status is of this issue? Perhaps something like what the `elasticsearch` and `chewy` gems do could be done here as well: https://github.com/toptal/chewy/blob/ac461c4d954c3f41f5677e216a19a1166d428190/README.md#aws-elastic-search Basically provide...

Yeah, if there were some kind of hook around `execute_request`, that would probably be even better! I agree it's weird to expose the internal HTTP library.

For reference, this is how the HTTP gem's instrumentation feature is used: https://github.com/httprb/http/wiki/Logging-and-Instrumentation.