You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cells is a great gem, and in my opinion should be part of core Rails. Kudos to Nick.
Sometimes though, it can be really hard to track down bugs. The error messages often are a long stacktrace. Othertimes, there are error messages with negative line numbers!
Is this a side effect of the way Cells hooks into Rails ... or could better error messages be somehow produced?
See the stacktrace below .. the actual error is triggered from a cell ruby class ... but where to start looking?
This might also have something to do with better_errors. I noticed that when I removed that gem, I was able to see the offending line inside my cell template.
Cells is a great gem, and in my opinion should be part of core Rails. Kudos to Nick.
Sometimes though, it can be really hard to track down bugs. The error messages often are a long stacktrace. Othertimes, there are error messages with negative line numbers!
Is this a side effect of the way Cells hooks into Rails ... or could better error messages be somehow produced?
See the stacktrace below .. the actual error is triggered from a cell ruby class ... but where to start looking?
The text was updated successfully, but these errors were encountered: