I've started setting up some plugins, and I noticed something which struck me as being a bit odd. I'm unsure if this behavior is by design or if it's a bug.
What seemed odd to me is that the order of precedence for settings in config files seems to be: APP trumps PLUGIN trumps PROJECT. I would have expected this to be APP trumps PROJECT trumps PLUGIN. As a concrete example... I have a plugin which contains a custom config file called config/core.yml. The plugin loads the config file in its config.php file. If I set up simple test core.yml files in the config directories for the plugin and the project, with different values for a test parameter, the value that is available to my pages is the value that was set in the project's core.yml file. However, if I add another core.yml file at the application level, then I get the value from the application's core.yml. What I expected is that a developer would want to set up default values for the plugin using the configuration file in the plugin's config file, and then override those values at either the project or application level. Please let me know if that behavior is not intended, I would be happy to file a bug. David Brewer --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
