acrib.es/wp-content/plugins/kadence-blocks/vendor/vendor-prefixed/stellarwp/prophecy-container

Prophecy Container

⚠️ This is a read-only repository! For pull requests or issues, see stellarwp/prophecy-monorepo.

The DI Container configuration and Service Provider implementation, utilizing di52.

Installation

Update your composer.json and add the following to your repositories object:

{
    "type": "vcs",
    "url": "git@github.com:stellarwp/prophecy-container.git"
}

Then, install:

composer require stellarwp/prophecy-container

Container Configuration

Create a new ContainerAdapter, by passing in an instance of di52:

<?php declare(strict_types=1);

namespace My\App;

use lucatume\DI52\Container;
use StellarWP\ProphecyMonorepo\Container\ContainerAdapter;

// Optionally, use the included vlucas/phpdotenv to load environment variables before the container.
$path = __DIR__;

if ( file_exists( $path . '/.env' )  ) {
    $dotenv = Dotenv::createImmutable( $path );
    $dotenv->load();
}

// This implements the Contracts/Container.php interface.
$container = new ContainerAdapter(new Container());

// Bind the concrete to the interface, so anytime we ask for a container we get this one.
$container->bind(Container::class, $container);

// Register our project's configuration. See "Making a config.php" below for more detail.
$container->bind(Dot::class, new Dot(require_once dirname(__FILE__) . '/config.php'));

// Register any service providers in the container.
$providers = [
   StellarWP\ProphecyMonorepo\Client\StorageProvider::class,
   // as many as you have made... 
];

foreach ( $providers as $provider ) {
    $container->register($provider);
}

Here is an example Service Provider:

<?php declare(strict_types=1);

namespace StellarWP\ProphecyMonorepo\Client;

use lucatume\DI52\ContainerException;
use StellarWP\ProphecyMonorepo\Container\Contracts\Provider;
use StellarWP\ProphecyMonorepo\Storage\Contracts\Storage;
use StellarWP\ProphecyMonorepo\Storage\Drivers\LocalStorage;

final class StorageProvider extends Provider
{
	/**
	 * @throws ContainerException
	 */
	public function register(): void {
		$this->container->bind(Storage::class, LocalStorage::class);
		$this->container->when(LocalStorage::class)
						->needs('$storagePath')
						->give($this->config->get('storage_path'));
	}
}

Environment Variable Configuration

This library uses the Dot package to set and fetch configuration values, which are initially provided via Environment Variables, either manually set or via an .env file utilizing vlucas/phpdotenv to read them.

Each Service Provider will have access to Dot via the $this->config property, it is best practice to only access configuration variables from a Service Provider and never in your concrete classes.

Making a config.php

A sample config.php for the Prophecy PHP Client. Note: we fall back to sane defaults if the environment variable isn't available.

<?php declare(strict_types=1);

return [
	'prophecy_key'    => $_ENV['PROPHECY_KEY'] ?? '',
	'prophecy_domain' => $_ENV['PROPHECY_DOMAIN'] ?? 'https://mydomain.com',
	'storage_path'    => $_ENV['PROPHECY_STORAGE_PATH'] ?? '/tmp',
	'log'             => [
		'level'    => $_ENV['PROPHECY_LOG_LEVEL'] ?? 'debug',
		'channel'  => $_ENV['PROPHECY_LOG_CHANNEL'] ?? 'null',
		'channels' => [
			'errorlog' => [],
			'console'  => [
				'with' => [
					'stream' => 'php://stdout',
				],
			],
		],
	],
	'rest_version'    => $_ENV['PROPHECY_REST_API_VERSION'] ?? 'v1',
];

Inside a Provider, we can then access deep variables with dot notation, e.g.

// Get the console log stream type from config.php.
$stream = $this->config->get('log.channels.console.with.stream');

// Get the log level.
$level = $this->config->get('log.level');

💡 If using a config.php in a WordPress plugin, simply add your configured $_ENV vars in your wp-config.php.

// Inside wp-config.php

// App configuration.
$_ENV['PROPHECY_DOMAIN'] = 'https://staging.mydomain.com'; 
$_ENV['PROPHECY_LOG_LEVEL'] = 'info';
$_ENV['PROPHECY_LOG_CHANNEL'] = 'errorlog';