I agree, it's easy knowledge to obtain, and I'd say it's not really even possible to use Merb effectively without knowing this major difference between it and Rails (actions returning strings, instead of internal rendering). One trying to use Merb without knowing this major difference would just be spinning their tires in the mud.
My main point is it's very common for Merb developers (who understand well how Merb actions and rendering mechanisms work) to also run into this error, which I did earlier. So the goal of improving error messages generated from the Merb internals isn't meant to allow Merb a seamless, thoughtfree transition from Rails. It's main goal would be to provide time saving assistence to the experts using Merb, so they can identify issues early, and save time debugging typos and accidental errors that inevitably creep into any nontrivial web project. On Jan 22, 9: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 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
