Better Rails errors

#1

Post by instakill » Sun, Dec 09, 2012, 8:57 AM UTC

Re: Better Rails errors

#2

Post by sirclueless » Sun, Dec 09, 2012, 10:26 AM UTC

This was always something of a killer feature for me in Python, and one of the reasons I use Flask a lot. Good to see Rails support for in-browser debugging, it's a super convenient workflow to never have to go back to the terminal, just alt-tab from editor to browser.

Re: Better Rails errors

#3

Post by shepbook » Sun, Dec 09, 2012, 10:43 AM UTC

As a Rails n00b, I can't wait to try this.

Re: Better Rails errors

#4

Post by patio11 » Sun, Dec 09, 2012, 10:45 AM UTC

An inline REPL? I love you more than I have words, particularly if you can somehow snag context for it.

Re: Better Rails errors

#5

Post by twinturbo » Sun, Dec 09, 2012, 10:52 AM UTC

patio11 wrote: post #4

An inline REPL? I love you more than I have words, particularly if you can somehow snag context for it.

That's why he's using binding_of_caller crap

Re: Better Rails errors

#6

Post by charliesome » Sun, Dec 09, 2012, 11:01 AM UTC

patio11 wrote: post #4

An inline REPL? I love you more than I have words, particularly if you can somehow snag context for it.

The REPL will execute code in the context of the currently selected stack frame.

Re: Better Rails errors

#7

Post by mtarnovan » Sun, Dec 09, 2012, 11:10 AM UTC

Seems super-useful. Thanks. I see you require binding_of_caller for advanced features (which exactly are those, btw?). That gem only works on 1.9. Do they work on 1.8.7 ? Does the gem work on 1.8.7 at all ?

Re: Better Rails errors

#8

Post by charliesome » Sun, Dec 09, 2012, 11:12 AM UTC

mtarnovan wrote: post #7

Seems super-useful. Thanks. I see you require binding_of_caller for advanced features (which exactly are those, btw?). That gem only works on 1.9. Do they work on 1.8.7 ? Does the gem work on 1.8.7 at all ?

binding_of_caller is required for the REPL and local/instance variable inspection. 1.8.x is not supported.

Re: Better Rails errors

#9

Post by richo » Sun, Dec 09, 2012, 11:15 AM UTC

What safeguards do you have in place to stop the unweary from sticking this into production?

While normally I'm a massive advocate of "Just not being retarded", I suspect a lot of people are going to drop shells as a result of this gem :(

Re: Better Rails errors

#10

Post by mylittlepony » Sun, Dec 09, 2012, 11:22 AM UTC

You guys would be amazed if you tried frameworks like Symfony (instead of discarding PHP for not being beautiful or whatever). It has always had these features, and in Symfony2 it only got more awesome. You even have a complete analysis for each request, that you can open with one click:

https://s3.amazonaws.com/i.imm.io/OvjX.jpeg

https://s3.amazonaws.com/i.imm.io/Ovk9.jpeg

Edit: Being downvoted. Some people just don't like knowing the truth.