Application trace in the error page for a Rails engine

17 views
Skip to first unread message

David Morales

unread,
Jul 7, 2014, 7:04:46 AM7/7/14
to rubyonra...@googlegroups.com
I'm developing a Rails engine, and when debugging an error through the default Rails error page, I find that the Application trace shows nothing, while Framework trace and Full trace show the trace.

Is this intended for an engine?

Andy Jeffries

unread,
Jul 7, 2014, 9:15:37 AM7/7/14
to rubyonra...@googlegroups.com
Yes, Engines are considered part of the framework level rather than the application level.  If I developed an engine and released it as a gem, you wouldn't want my lines littering your application stack trace, right?

Cheers,


Andy

Andy Jeffries Ruby on Rails, RubyMotion, jQuery Developer & Taekwondo 6th Dan Instructor
andyjeffries.co.uk +44 7939 164853 @andyjeffries fb.com/andyjeffries


On 7 July 2014 12:04, David Morales <davidmora...@gmail.com> wrote:
I'm developing a Rails engine, and when debugging an error through the default Rails error page, I find that the Application trace shows nothing, while Framework trace and Full trace show the trace.

Is this intended for an engine?

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-ta...@googlegroups.com.
To post to this group, send email to rubyonra...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/76da4720-e598-4550-9e56-9f832ceb6623%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages