https://github.com/thecodingmachine/factory-to-definition
[EXPERIMENTAL] This package tries to convert (if possible) factories of service providers into definition-interop compatible definitions.
https://github.com/thecodingmachine/factory-to-definition
Last synced: 11 months ago
JSON representation
[EXPERIMENTAL] This package tries to convert (if possible) factories of service providers into definition-interop compatible definitions.
- Host: GitHub
- URL: https://github.com/thecodingmachine/factory-to-definition
- Owner: thecodingmachine
- Created: 2016-04-05T13:05:16.000Z (about 10 years ago)
- Default Branch: 1.0
- Last Pushed: 2016-04-05T15:24:54.000Z (about 10 years ago)
- Last Synced: 2025-06-30T03:09:37.284Z (12 months ago)
- Language: PHP
- Size: 14.6 KB
- Stars: 0
- Watchers: 7
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
Warning, experimental project!
------------------------------
[](https://scrutinizer-ci.com/g/thecodingmachine/factory-to-definition/?branch=1.0)
[](https://travis-ci.org/thecodingmachine/factory-to-definition)
[](https://coveralls.io/github/thecodingmachine/factory-to-definition?branch=1.0)
What is it?
===========
This project is a crazy attempt to create a bridge between [container-interop's service providers](http://github.com/container-interop/service-provider)
and [container-interop's definition interfaces](http://github.com/container-interop/definition-interop/).
But why?
========
It should be pretty easy to take container definitions and compile them into a service provider class (this is a
standard compilation pass). What I'm trying to do here is the opposite. Take a service provider (i.e. a set of
factory methods in pure PHP code), and cast those into service definitions.
Let's be clear, this is not obviously not always possible. Still, I'm trying to do it for very simple use cases.
Why?
- Because it's fun
- Because it might bring very slight improvements to performances for compiled container (they can optimize container definition, but they cannot optimize factory methods).
What can it do so far?
======================
Not much, really!
It can:
- detect aliases and transform those into `Interop\Container\Definition\ReferenceDefinitionInterface` :
```php
public static function alias(ContainerInterface $container)
{
return $container->get('foo');
}
```
will map to a `ReferenceDefinition` object pointing to the `foo` container entry.
- detect static values / parameters and transform those into `Interop\Container\Definition\ParameterDefinitionInterface` :
```php
public static function scalar()
{
return 'my_value';
}
```
will map to a `ParameterDefinition` object containing `my_value` as a value. Note: as per the definition-interop unit test suite, a `ParameterDefinition` can be anything from a static string / number to an array of scalar values. Arrays also accept references.
And that's it for now!