I agree that using views/exceptions/[error].html.erb is appropriate in some cases, and I do. But for overall protection against data errors and other real problems that I do indeed want to hide from the end user, I want to rescue exceptions as close to the error as possible so I can render as much of the page as possible. Of course I'll log these errors so they're only hidden from the end user, not from me.
On Mon, Dec 29, 2008 at 4:37 PM, Michael Klishin < [email protected]> wrote: > > > On 30.12.2008, at 1:46, David Kovsky wrote: > > > Am I doing something wrong above? > > > rescuing exceptions in views is just hiding real problems, either with > what controller fetches from the data store, or data integrity (nil > pointer, blah, blah). > > Exceptions in Merb are re-routed so you can show user a useful page > instead of 404 or 500. What you really should be doing is adding > templates to views/exceptions/not_found.html.*, views/exceptions/ > non_acceptable.html.* and so forth. controller that handles exceptions > by default is provided by Merb core. > > MK > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/merb?hl=en -~----------~----~----~----~------~----~------~--~---
