Hi Moritz, when discovering this I created the test 't/model/hashref_create_repeatable_without_nestedname.[t|yml]' to validate that we die correctly.
The problem is, that there is no intelligent solution as it just doesn't make much sense to me to use a Repeatable without a nested name. Greets, Mario Am Dienstag 30 Juni 2009 14:32:56 schrieb Moritz Onken: > Am 18.05.2009 um 16:25 schrieb Mario Minati: > > During my work on rewriting the Repeatable element for an easier > > client side > > javascript handling I found out that Model::HashRef cannot handle > > Repeatable > > elements without nested_name. > > > > The function get_repeatable just ignores them. > > > > To save users from running to that problem I changed the code of > > FF::Model::HashRef to die if there is a Repeatable without name > > (rev. 1509). > > > > > > Greets, > > > > Mario Minati > > Hi Mario, > > could you supply a test which dies? Then I can try to hack something > together so that HashRef can cope with Repeatables without a nested > name. > > How do the names of elements inside a repeatable block look like if > you have no nested name? > > repeatable_1.foo > repeatable_2.foo > > is AFAIK the current behaviour for nested_named repeatables. > > moritz > > > _______________________________________________ > HTML-FormFu mailing list > HTML-FormFu@lists.scsys.co.uk > http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/html-formfu _______________________________________________ HTML-FormFu mailing list HTML-FormFu@lists.scsys.co.uk http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/html-formfu
