Hi all, The default_exception controller/view in Merb is one of the most oustanding I've seen, especially with the slick javascript.
I wanted to do the following: - do additional logging (such as a timestamp of when the exception occurred and a guid search for in the logfile to link it up with an offsite bug repository) - do additional reporting (like post the exception to a google spreadsheet) - keep all the prettiness of the original view but customize the text - instead of showing details only when env? :development, also when session.user is recognized to be a developer I accomplished the above by copying the default_exception controller and views from merb-core/dispatch into app/views/exceptions (which means that there's a controller in the exceptions view and a views directory inside exceptions, kinda icky). I'd love to make directory structure cleaner. As well it would be great for more customization to be exposed to the developer without having to cut-and-paste from merb-core, which feels really fragile. Anyone else done anything like this or had a better strategy? Thanks, Gary --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
