MK: I think it makes sense to provide a warning here. A nil body will always error, so why not catch the error and print a useful warning?
-- Yehuda On Thu, Jan 22, 2009 at 10:43 PM, Michael Klishin < [email protected]> wrote: > > > On 23.01.2009, at 8:34, Jacques Crocker wrote: > > > However... I don't think this fact excludes the usefulness of > > providing helpful error messages in the framework internals for common > > errors cases (nil body is a very, very common one). > > > It is common among people who just came to Merb from Rails, and only > need to figure out that there is no autorendering > and render/display both return strings. This is something one must > figure out to do anything with Merb, and I don't mean studying > internals here. > Just read a wiki page. > > MK > > > > > -- Yehuda Katz Developer | Engine Yard (ph) 718.877.1325 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
