https://github.com/decodelabs/veneer
Automated static frontages for PHP
https://github.com/decodelabs/veneer
facade frontage php
Last synced: 2 months ago
JSON representation
Automated static frontages for PHP
- Host: GitHub
- URL: https://github.com/decodelabs/veneer
- Owner: decodelabs
- License: mit
- Created: 2019-09-10T23:08:20.000Z (about 6 years ago)
- Default Branch: develop
- Last Pushed: 2025-06-06T12:58:42.000Z (4 months ago)
- Last Synced: 2025-07-08T12:03:43.464Z (3 months ago)
- Topics: facade, frontage, php
- Language: PHP
- Homepage:
- Size: 222 KB
- Stars: 3
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
Awesome Lists containing this project
README
# Veneer
[](https://packagist.org/packages/decodelabs/veneer)
[](https://packagist.org/packages/decodelabs/veneer)
[](https://packagist.org/packages/decodelabs/veneer)
[](https://github.com/decodelabs/veneer/actions/workflows/integrate.yml)
[](https://github.com/phpstan/phpstan)
[](https://packagist.org/packages/decodelabs/veneer)
### Create automated static frontages for your PHP objects.
Use Veneer to provide easy access to your most commonly used functionality without sacrificing testability.
---
## Install
```bash
composer require decodelabs/veneer
```
## Usage
Say you have a common library class you use regularly:
```php
namespace Some\Random\Library;
// This is a library class you use regularly
class MyThing
{
public function doAThing() {
echo 'Done!';
}
}
```
You can bind a static, automatically generated frontage by:
```php
namespace App\Setup;
// This is your environment setup code
use DecodeLabs\Veneer;
use Some\Random\Library\MyThing;
use App\CoolThing;
Veneer::register(
MyThing::class, // active object class
CoolThing::class // frontage class
);
namespace Some\Other\Code;
use App\CoolThing;
// Your general userland code
CoolThing::doAThing();
```
### Plugins
Unfortunately PHP still doesn't have \__getStatic() yet so we have to statically declare plugin names at binding time, but they're still useful for creating more expansive interfaces.
Define plugins as properties on your FacadeTarget with a Plugin attribute. By default, plugins require manual instantiation in the constructor, however you can flag it as auto to have it automatically built at bind time, or lazy if it doesn't need to be loaded straight away.
```php
namespace My\Library
{
use DecodeLabs\Veneer\Plugin;
class MyThing {
#[Plugin]
public MyPlugin $plugin;
#[Plugin(auto: true)]
public MyPlugin $autoPlugin;
#[Plugin(lazy: true)]
public MyPlugin $lazyPlugin;
public function __construct() {
$this->plugin = new MyPlugin();
}
}
class MyPlugin
{
public function doAThing(): string {
return 'Hello from plugin';
}
}
}
namespace Some\Other\Code
{
use My\Library\MyThing;
MyThing::$plugin->doAThing(); // Hello from plugin
MyThing::$autoPlugin->doAThing(); // Hello from plugin
MyThing::$lazyPlugin->doAThing(); // Hello from plugin
}
```
Note, if your target class has a constructor with required parameters, you will need to add decodelabs/slingshot to your project to allow Veneer to instantiate it.
Lazy instantiation uses the new ghost and proxy functionality in PHP8.4 and will only instantiate the plugin when it is first accessed. Due to the limitations of lazy objects in PHP, you cannot create a lazy proxy for internal classes so you may find that plugins are referenced with a transparent Plugin\Wrapper class which resolves to the actual plugin instance when accessed. This usually isn't an issue unless you try to pass a plugin instance to a function that expects a specific class type, directly from the proxy. In these cases you should return the plugin instance from a method on the target class.
### Property Hooks
PHP 8.4 property hooks can be used in combination with Plugins, however be aware that they will conflict with auto and lazy instantiation. Hooks defined with the structure below will effectively act like a lazy loaded plugin, however with the additional benefits of being able to control how it is instantiated rather than relying on Slingshot.
```php
namespace My\Library
{
use DecodeLabs\Veneer\Plugin;
class MyThing {
#[Plugin]
protected(set) MyPlugin $plugin {
get => $this->plugin ??= new MyPlugin();
}
}
}
```
Hooks _can_ be virtual (ie, don't require a value backed property), however the proxy will reference the first instantation of a virtual hook and your plugin instances will likely go out of sync.
Note, the protected(set) visibility in the example; it is not a requirement, but it is recommended to prevent direct write access to the property. If you need to replace a plugin instance, you should do so via Veneer::replacePlugin(\$providerInstance, \'propertyName\', \$newPlugin). This allows Veneer to update the plugin in the static frontage proxy as well as the target instance.
## Licensing
Veneer is licensed under the MIT License. See [LICENSE](./LICENSE) for the full license text.