webware / webware-configmanager
Nested object property based access to configuration data, with pluggable readers, writers and processors.
Requires
- php: ~8.4.1 || ~8.5.0
- ext-json: *
- brick/varexporter: ^0.7.0
- php-standard-library/type: ^6.4.2
- psr/container: ^2.0
- webware/webware-filewriter: ^1.0.0-alpha.2
Requires (Dev)
- infection/infection: ^0.35.0
- laminas/laminas-config-aggregator: 1.21
- laminas/laminas-filter: ^3.5
- laminas/laminas-i18n: ^3.1
- laminas/laminas-servicemanager: ^4.6
- phpbench/phpbench: ^1.7
- phpunit/phpunit: ^13.3.0
- roave/backward-compatibility-check: ^8.21.0
- roave/security-advisories: dev-master
- symfony/yaml: ^7.4 || ^8.0
- webware/webware-tools: 1.0.0-rc.15
Suggests
- laminas/laminas-filter: Install to use the Filter processor
- laminas/laminas-i18n: Install to use the Translator processor
- laminas/laminas-servicemanager: Install if you need an extensible plugin manager for use with the Config Factory
Provides
None
Conflicts
None
Replaces
None
This package is auto-updated.
Last update: 2026-11-17 01:04:27 UTC
README
Nested object property based access to configuration data, with pluggable readers, writers and processors.
This package is the fork of laminas/laminas-config and a drop-in replacement for
laminas/laminas-config-aggregator, so one package supplies both the aggregator and the
configuration object it produces.
Installation
composer require webware/webware-configmanager
Documentation
Usage
use Webware\ConfigManager\Config; use Webware\ConfigManager\Factory; $config = new Config([ 'db' => [ 'host' => '127.0.0.1', 'name' => 'webware', ], ]); echo $config->db->host; // 127.0.0.1
Factory reads and writes .ini, .json, .xml, .yaml/.yml, .properties and .php files, and
merges several files into one configuration:
$config = Factory::fromFiles(['config/autoload/global.php', 'config/autoload/local.php'], true);
Readers and writers are resolved through ReaderPluginManager and WriterPluginManager when
laminas/laminas-servicemanager is installed, and through the standalone plugin managers otherwise.
Both resolve a plugin by fully qualified class name and by file extension; ConfigProvider declares
those aliases, and the extension map Factory uses is read from the same declarations.
Replacing laminas-config-aggregator
ConfigAggregator takes the same arguments in the same order and getMergedConfig() returns the
same array, so replacing the aggregator is a class name change. ArrayProvider and PhpFileProvider
are here too.
use Webware\ConfigManager\ConfigAggregator; use Webware\ConfigManager\Provider\PhpFileProvider; $aggregator = new ConfigAggregator( [ \Mezzio\ConfigProvider::class, new PhpFileProvider(realpath(__DIR__) . '/autoload/{{,*.}global,{,*.}local}.php'), ], 'data/cache/config-cache.php', ); return $aggregator->getMergedConfig();
Because ConfigAggregator extends Config, the merged result is the configuration rather than an
array that has to be wrapped: get(), array access, iteration and toArray() all work on it.
getMergedConfig() remains for the aggregator's own signature. The ENABLE_CACHE and
CACHE_FILEMODE constants are redeclared on it, so existing references keep resolving. For the
deprecated LaminasConfigProvider, use Factory::fromFiles().
Declaring merge order
A provider can declare its position instead of relying on where it appears in the list, which matters
because laminas-component-installer prepends what it writes, so a package installed last lands
first and loses every key it shares with a package it builds on.
use Webware\ConfigManager\Attribute\LoadAfter; #[LoadAfter(OtherProvider::class)] final class ConfigProvider { /** @return array<array-key, mixed> */ public function __invoke(): array { return []; } }
#[LoadBefore] is the counterpart and both accept several targets. A provider that declares nothing
keeps the position it was given, a target that is not installed is ignored, and a cycle is reported
as an exception naming its participants.
Origin
Forked from laminas/laminas-config 3.12.x, which remains BSD-3-Clause licensed. See LICENSE.md
and COPYRIGHT.md.