Added support for setting priority of config files #26
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Configuration in parameters section of config files had hardcoded higher priority than configuration passed from parameters array passed to Compiler::compile.
I found this unhandy, because sometimes I need to override some configuration from config files in my bootstrap. It seems more logical for me that dynamically built parameters in bootstrap.php have higher priority than static config files.
For backwards compatibility, I've made this behavior optional, configurable by ContainerFactory::$configPriority.
I issued another pull request for nette/bootstrap, which which should allow to set $configurator->configPriority in bootstrap without needing to manually call ContainerFactory.