Great work on the new release of Maypole :)
I'm just going through modifying my application to conform to the new
classes and thought I'd note down any issues as I found them.
I think I've found a bug in Maypole.pm, where it sets display_tables:
$config->display_tables
# || $config->display_tables( [ $class->config->tables ] );
|| $config->display_tables( $class->config->tables );
The result of tables seems to be a reference (should it be?) and it's
necessary to remove the square brackets (original line is commented out)
to get display_tables initialised so it works. Otherwise frontpage
displays an empty list!
BTW, thanks for the config->loader hook :)
Here are other small documentation snags I've found so far:
Maypole::Config
---------------
There are a few methods/attributes/properties where there's apparently a
discrepancy between the code and docs:
application_name, tables and table_to_class are not described.
document_encoding, content_type and models are present in the code but
probably shouldn't be?
Is there any significance in the order in which methods are listed? If
so, it would be good to explain it. If not, alphabetical order would be
nice :)
Cheers, Dave
_______________________________________________
maypole mailing list
maypole at lists.netthink.co.uk
http://lists.netthink.co.uk/listinfo/maypole
This archive was generated by hypermail 2.1.3 : Thu Feb 24 2005 - 22:25:56 GMT