Automatically wire up middleware for rails apps about miniprofiler HOT 6 CLOSED

see: http://stackoverflow.com/questions/10135147/why-does-this-method-fail-to-instrument-actionviewtemplate-render

from miniprofiler.

Is this comment on the right issue? Because I fixed a bug with
instrumenting the render (other issue) and it seems to work for me!

On Fri, Apr 13, 2012 at 12:19 AM, Sam
[email protected]
wrote:

see: http://stackoverflow.com/questions/10135147/why-does-this-method-fail-to-instrument-actionviewtemplate-render

---

Reply to this email directly or view it on GitHub:
#27 (comment)

from miniprofiler.

oops, should not have asked that

getting a sane name seems to be quite challenging
x.instance_variable_get '@virtual_path'

seems to get us a bit of info ... but it is not enough

from miniprofiler.

oops apologies ... yeah my mistake my patch was not needed, though we still need to figure out a way of getting nice names for the partials etc

from miniprofiler.

k ... I think I got it working now for views ... still need to wire up rack middleware

from miniprofiler.

Okay, this is working now in my Rails project automatically.

It defaults to off unless the environment is development.

I have added a configuration method so you can configure it in rails with an initializer since you don't have access to the constructor.

Here's an example from my project, where I want it visible in development and production:

# config/initializers/mini_profiler.rb
Rack::MiniProfiler.configuration[:authorize_cb] = lambda {|env| true }

from miniprofiler.