The manual doesn't state that order is important - http://cookbook.hobocentral.net/manual/hobo_fields/api - but it appears that :required sometimes has to immediately follow the type, and sometimes doesn't. For example when I try a hobo migration including this field:
percentage :decimal, :scale => 1, :precision => 3, :required it creates an error message about expecting a "\n" in tASSOC. But: percentage :decimal, :required, :scale => 1, :precision => 3 works (creates a migration). However: value enum_string(:first, :second, :third), :required seems to work. So :required isn't always required immediately after the column type. I suspect this is a bug rather than a documentation oversight, because the order of declaration is sensitive to the types involved? I've also got a case where a nested set of :accessible models causes a complete rails crash through what looks like a null pointer dereference? Should I be posting these problems here? Is it helpful if I make a test case and share it on GitHub? It feels ungrateful to keep posting problems, but I'm sufficiently new to both Hobo and Rails that I'm finding more problems than solutions : ( Cheers, JeremyC. -- You received this message because you are subscribed to the Google Groups "Hobo Users" 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/hobousers?hl=en.
