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.
I've added a compatibility layer for the INI config so that it can be used in PHP-DI config.
In order to avoid conflicts in config keys (between DI config and INI config), INI config is prefixed with
old_config
(so that it's easy to see which configs will be eventually replaced)Entry names are formatted like this:
old_config.<section>.<key>
, for example:old_config.database.host
would be the same as callingConfig::getInstance()->database['host']
.FYI you can also get a whole section as array, i.e.
old_config.database
is the same asConfig::getInstance()->database
.That also mean that we can alias INI config entries into DI config, e.g.:
(in that example
logger.level
is an alias to the old config key, if you are lost by the syntax read here)I'm not saying we should do all aliases now, but that will be useful to work on #6622 (configuring the logger in DI config while still using the old INI values for BC).