Configuration Provider System

The ConfigProviderRegister class serves as the central registry for managing configuration providers within the Hypervel Testbench framework. This class maintains a static collection of 45 service providers from both Hyperf and Hypervel frameworks, enabling modular application architecture and ensuring consistent service registration during test execution.

For information about how these providers are used during application bootstrapping, see page 5. For details on configuring which providers are active, see page 6.1.

Class Overview

The ConfigProviderRegister class is a static utility located in src/ConfigProviderRegister.php that manages service provider registration for the testbench environment. It provides methods to retrieve, filter, add, and remove configuration providers that define services, dependencies, and framework components.

Class Structure and API Surface

Sources: src/ConfigProviderRegister.php9-88

System Integration

Sources: src/ConfigProviderRegister.php9-88

Provider Registry Structure

The class maintains a comprehensive list of configuration providers organized by framework. The static $configProviders array contains exactly 45 provider classes that are essential for testbench functionality.

Hyperf Framework Providers (20 Total)

The registry includes 20 core Hyperf providers that handle fundamental framework services:

Provider Class	Line	Purpose
Hyperf\Command\ConfigProvider	12	CLI command system registration
Hyperf\Database\SQLite\ConfigProvider	13	SQLite database driver support
Hyperf\DbConnection\ConfigProvider	14	Database connection management
Hyperf\Di\ConfigProvider	15	Dependency injection container
Hyperf\Dispatcher\ConfigProvider	16	Event dispatcher system
Hyperf\Engine\ConfigProvider	17	Swoole coroutine engine integration
Hyperf\Event\ConfigProvider	18	Event listener registration
Hyperf\ExceptionHandler\ConfigProvider	19	Exception handling middleware
Hyperf\Framework\ConfigProvider	20	Core framework bootstrapping
Hyperf\HttpMessage\ConfigProvider	21	PSR-7 HTTP message implementations
Hyperf\HttpServer\ConfigProvider	22	HTTP server and routing
Hyperf\Memory\ConfigProvider	23	Memory table abstractions
Hyperf\ModelListener\ConfigProvider	24	Eloquent model event listeners
Hyperf\Paginator\ConfigProvider	25	Database query pagination
Hyperf\Pool\ConfigProvider	26	Connection pooling infrastructure
Hyperf\Process\ConfigProvider	27	Process management
Hyperf\Redis\ConfigProvider	28	Redis client and pooling
Hyperf\Serializer\ConfigProvider	29	Data serialization handlers
Hyperf\Server\ConfigProvider	30	Server configuration and lifecycle
Hyperf\Signal\ConfigProvider	31	Signal handling for process control

Hypervel Framework Providers (25 Total)

The registry includes 25 Hypervel providers that extend Hyperf with Laravel-inspired features:

Provider Class	Line	Purpose
Hypervel\ConfigProvider	32	Base Hypervel framework services
Hypervel\Auth\ConfigProvider	33	Authentication guards and providers
Hypervel\Broadcasting\ConfigProvider	34	WebSocket and event broadcasting
Hypervel\Bus\ConfigProvider	35	Command bus and job dispatching
Hypervel\Cache\ConfigProvider	36	Cache manager and drivers
Hypervel\Cookie\ConfigProvider	37	HTTP cookie management
Hypervel\Config\ConfigProvider	38	Configuration repository
Hypervel\Console\ConfigProvider	39	Artisan-style console commands
Hypervel\Dispatcher\ConfigProvider	40	Event dispatcher integration
Hypervel\Encryption\ConfigProvider	41	Data encryption services
Hypervel\Event\ConfigProvider	42	Event system and listeners
Hypervel\Foundation\ConfigProvider	43	Application foundation layer
Hypervel\Hashing\ConfigProvider	44	Password hashing (bcrypt, argon2)
Hypervel\Http\ConfigProvider	45	HTTP kernel and middleware
Hypervel\JWT\ConfigProvider	46	JWT authentication tokens
Hypervel\Log\ConfigProvider	47	Monolog logging integration
Hypervel\Mail\ConfigProvider	48	Email sending services
Hypervel\Notifications\ConfigProvider	49	Multi-channel notifications
Hypervel\ObjectPool\ConfigProvider	50	Object pooling for performance
Hypervel\Queue\ConfigProvider	51	Job queue workers and connections
Hypervel\Redis\ConfigProvider	52	Redis cache and session drivers
Hypervel\Router\ConfigProvider	53	HTTP routing system
Hypervel\Session\ConfigProvider	54	Session storage and management
Hypervel\Translation\ConfigProvider	55	Internationalization (i18n)
Hypervel\Validation\ConfigProvider	56	Request validation rules

Sources: src/ConfigProviderRegister.php11-57

Provider Registration Flow

Sources: src/ConfigProviderRegister.php11-66

Dynamic Provider Detection

The get() method implements conditional provider loading, specifically checking for the optional Hyperf\Devtool\ConfigProvider:

This approach allows the testbench to automatically detect and include development tools when available, without creating hard dependencies. The devtool provider adds debugging, profiling, and inspection capabilities.

Sources: src/ConfigProviderRegister.php59-66

Provider Management API

The class provides four static methods for managing the provider registry:

Method Reference Table

Method	Parameters	Return Type	Mutates Registry	Purpose
get()	None	array	No	Retrieve all registered providers with optional devtool
filter()	callable $callback	array	Yes	Filter providers using callback and update registry
add()	array|string $providers	void	Yes	Append new providers to registry
except()	array|string $providers	void	Yes	Remove specified providers from registry

Sources: src/ConfigProviderRegister.php59-87

get() Method Implementation

Returns the provider array, conditionally including the devtool provider if available.

Sources: src/ConfigProviderRegister.php59-66

filter() Method Implementation

Applies array_filter() with a custom callback to the provider list. The filtered result is assigned back to static::$configProviders, making this a mutating operation.

Example Usage:

Sources: src/ConfigProviderRegister.php68-71

add() Method Implementation

Appends providers to the registry. Uses Arr::wrap() from Hyperf\Collection\Arr to normalize string or array input into an array.

Example Usage:

Sources: src/ConfigProviderRegister.php73-79

except() Method Implementation

Removes providers from the registry using array_diff(). Also uses Arr::wrap() for input normalization.

Example Usage:

Sources: src/ConfigProviderRegister.php81-87

Registry Manipulation Flow

Sources: src/ConfigProviderRegister.php68-87

Integration with Bootstrap Process

The ConfigProviderRegister plays a crucial role in the testbench initialization sequence by providing the complete list of service providers that need to be registered during application bootstrap:

This centralized approach ensures that all necessary framework components are consistently available across different test scenarios while maintaining the flexibility to customize the provider set for specific testing requirements.

Sources: src/ConfigProviderRegister.php59-66