I'd like to propose a filename convention for the configuration classes that matches the convention currently in use for module actions classes. The filename "ProjectConfiguration.class.php" is repetitive, since the file lives in the project level config directory. Likewise, "frontendConfiguration.class.php" is repetitive since that file lives in /apps/frontend/config.
Do DRY principles apply here? The "default" module's actions class is called "defaultActions" but the filename is called "actions.class.php". Why not store the configuration classes in "configuration.class.php" ??? Thanks all, Kris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" 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/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
