He's right. It *would* be nice to have mock-objects. Actually, can't you do a datamapper object which stores objects in memory only while the others store their data in other places?
By the way, how does datamapper handle multiple databases? Julian. On 08/10/2008, at 10:38 AM, Michael Klishin wrote: > > 2008/10/8 Christian von Kleist <[EMAIL PROTECTED]>: >> >> I have a simple form which collects options. The options won't be >> stored in a database -- my app is tiny and doesn't use a database -- >> but I'd like to use form_for and all its wonderful goodness. >> >> class Options >> attr_accessor :setting1, :setting2, :setting3 >> end >> >> What class can Options extend to be usable with form_for? > > You can define errors method that returns an empty array. It's a known > problem. I am slowly moving merb-helpers spec suite to real models, > so this gonna be fixed before 1.0. This case wasn't take into account > but it's been reported several times already. > -- > 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 -~----------~----~----~----~------~----~------~--~---
