The only thing I can think is that the for-type is throwing things off somehow. I know if you specify type, it reverts back to a regular input tag. If not, might help to see a little more context around that.
On Aug 11, 1:44 pm, Skott Klebe <[email protected]> wrote: > Here's a follow-on that's been baffling me UNTIL I looked at the generated > HTML: > When I use one of these special_tags as Matt describes below, I get a > blank string in the HTML id field. > > #{scope.field_name.to_s.sub('?', '').sub('.', '-')}-tag > > For example: > > <note-view:><input class="note" for-type="text" rows="4"/></note-view:> > > in a form, I'm getting a field that looks like this: > > <textarea class="note" id="" rows="4"></textarea> > > Since the generated code doesn't specify a value for the id attribute, > the controller logic doesn't extract the value and stick it into the > model to be saved. > > SK > > > > > > >> doesn't make it perfectly clear that a field named 'special_field' > >> will turn into a param named special-field-tag? Surely *everyone* can > >> read Ruby hieroglyphics! :) > > >> That's definitely one of the more opaque sections of the docs. > > >> --Matt Jones > > > -- > > 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 > > athttp://groups.google.com/group/hobousers?hl=en. > > -- > Skott Klebe > [email protected] -- 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.
