kassko/class-resolver-bundle

Integrate the class-resolver component to Symfony

Monday, June 6, 2016
by kassko
Repository
1 Watchers
0 Stars
5,927 Installations

PHP
1 Dependents
0 Suggesters
0 Forks
0 Open issues
18 Versions
3 % Grown

The README.md

class-resolver-bundle

, _(*1)

Bundle which integrates class-resolver into Symfony. Please for natives features, take a look at the class-resolver documentation., _(*2)

Installation

You can install this component with composer composer require kassko/class-resolver-bundle:some_version, _(*3)

You also need to register the bundle to your kernel:, _(*4)

public function registerBundles()
{
    $bundles = array(
        new Kassko\Bundle\ClassResolverBundle\KasskoClassResolverBundle(),
    );
}

There are two differents ways to use the class-resolver

Example of semantic configuration

kassko_class_resolver:
    container_adapter_class: Kassko\Bundle\ClassResolverBundle\Adapter\Container\SymfonyContainerAdapter # default
    resolver_aliases:
        alias_one: my_container_resolver_service_one
        # - {alias_one: my_container_resolver_service_one}
    resolvers:
        container:
            [my_container_resolver_service_one, my_container_resolver_service_two]
            # or
            # - { resolver_service: my_container_resolver_service_one, resolver_aliases: [alias_two] }
            # - { resolver_service: my_container_resolver_service_two }
        map:
            map_one:
                resolver_service: my_map_resolver_service_one
                items:
                    "My\\Namespace": my_service_one
                    "My\\Namespace\\Two": my_service_two
                    # or
                    # - { class: "My\\Namespace", service: my_service_one }
                    # - { class: "My\\Namespace\\Two", service: my_service_two }
        factory_adapter:
            - resolver_service: my_factory_adapter_resolver_service_one
              adapted_service: my_adapted_service_one
              support_method: supports
              resolve_method: resolve
            - resolver_service: my_factory_adapter_resolver_service_two
              adapted_service: my_adapted_service_two
              support_method: supports
              resolve_method: resolve 
            # or with the following syntax
            - {resolver_service: adapter_one, adapted_factory: resolver_one} # etc            
        static_factory_adapter:
            - resolver_service: my_static_factory_adapter_resolver_service_one
              adapted_class: my_static_resolver_class
              support_method: supports
              resolve_method: resolve
            - resolver_service: my_static_factory_adapter_resolver_service_two
              adapted_class: my_static_resolver_class
              support_method: supports
              resolve_method: resolve
            # or with the following syntax
            - {resolver_service: adapter_two, adapted_factory: resolver_two} # etc

You can define some class resolvers in semantic configuration and use them in you service configuration file

<service id="some_service_a" class="stdClass">
    <argument id="my_map_resolver_service_one" type="service" />
</service>

<service id="some_service_b" class="stdClass">
    <argument id="my_factory_adapter_resolver_service" type="service" />
</service>

<service id="some_service_c" class="stdClass">
    <argument id="my_static_factory_adapter_resolver_service" type="service" />
</service>

You can both define some class resolvers on the fly and feed them with pairs [class, service] all from your service configuration file

You register your service like pairs [class, service] to a resolver you create on the fly:, _(*5)

<service id="some_service_a" class="stdClass">
    <argument id="my_container_resolver_service_one" type="service" />
    <!-- create a resolver on the fly identified by its group -->
    <tag name kassko_class_resolver.add group="a_group_name_choosen_by_you"> 
</service>

<service id="some_service_b" class="stdClass">
    <argument id="my_container_resolver_service_one" type="service" />
    <!-- use the resolver previously created in the service `some_service_a` -->
    <tag name kassko_class_resolver.add group="a_group_name_choosen_by_you"> 
</service>

And you inject the good resolver (identified by it's group) in the concerned services:, _(*6)

<service id="some_service_c" class="stdClass">
    <tag name kassko_class_resolver.inject group="a_group_name_choosen_by_you">
</service>

A group is a way not to manipulate some service., _(*7)

This way to do has the advantage to add some new resolvers without changing the semantic configuration and to use work with only one file (the service configuration file)., _(*8)

For more information about this last feature, please read the more detailed documentation, _(*9)

Finally, you can use some class resolvers defined on the semantic configuration and feed them from your service configuration file

You register your service like a pair [class, service] in the already existing resolver my_container_resolver_service_one:, _(*10)

<service id="some_service_a" class="stdClass">
    <tag name kassko_class_resolver.add service="my_container_resolver_service_one">
</service>

You inject the resolver my_container_resolver_service_one in a service which need it:, _(*11)

<service id="some_service_a" class="stdClass">
    <argument id="my_container_resolver_service_one" type="service" />
</service>

The Versions

06/06 2016

dev-kassko-try

Integrate the class-resolver component to Symfony

Sources Download

The Requires

The Development Requires

phpunit/phpunit ~4.4

by kassko

class resolver factory dependency injection

02/06 2016

dev-master

9999999-dev

Integrate the class-resolver component to Symfony

Sources Download

The Requires

The Development Requires

phpunit/phpunit ~4.4

by kassko

class resolver factory dependency injection

02/06 2016

v0.3.3.0

0.3.3.0

Integrate the class-resolver component to Symfony

Sources Download

The Requires

The Development Requires

phpunit/phpunit ~4.4

by kassko

class resolver factory dependency injection

02/06 2016

dev-kassko-new_resolvers

Integrate the class-resolver component to Symfony

Sources Download

The Requires

The Development Requires

phpunit/phpunit ~4.4

by kassko

class resolver factory dependency injection

29/11 2015

v0.3.2.0

0.3.2.0

Integrate the class-resolver component to Symfony

Sources Download

The Requires

The Development Requires

phpunit/phpunit ~4.4

by kassko

class resolver factory dependency injection

25/03 2015

v0.3.1.0

0.3.1.0

Integrate the class-resolver component to Symfony

Sources Download

The Requires

The Development Requires

phpunit/phpunit ~4.4

by kassko

class resolver factory dependency injection

06/03 2015

v0.3.0.1-alpha

0.3.0.1-alpha

Integrate the class-resolver component to Symfony

Sources Download

The Requires

The Development Requires

phpunit/phpunit ~4.4

by kassko

class resolver factory dependency injection

05/01 2015

v0.3.0.0-alpha

0.3.0.0-alpha

Integrate the class-resolver component to Symfony

Sources Download

The Requires

The Development Requires

phpunit/phpunit ~4.4

by kassko

class resolver factory dependency injection

15/12 2014

0.2.0-alpha.8

0.2.0.0-alpha8

Integrate the class-resolver component to Symfony

Sources Download

The Requires

The Development Requires

phpunit/phpunit ~4.4

by kassko

class resolver factory dependency injection

15/12 2014

0.2.0-alpha.7

0.2.0.0-alpha7

Integrate the class-resolver component to Symfony

Sources Download

The Requires

The Development Requires

phpunit/phpunit ~4.4

by kassko

class resolver factory dependency injection

04/11 2014

0.2.0-alpha.6

0.2.0.0-alpha6

class-resolver integrated to Symfony.

Sources Download

The Requires

by kassko

class resolver factory dependency injection

03/11 2014

0.2.0-alpha.5

0.2.0.0-alpha5

class-resolver integrated to Symfony.

Sources Download

The Requires

by kassko

class resolver factory dependency injection

02/11 2014

0.2.0-alpha.4

0.2.0.0-alpha4

class-resolver integrated to Symfony.

Sources Download

The Requires

php >=5.5.0
symfony/framework-bundle ~2.5
kassko/class-resolver ~0.1@alpha
kassko/common ~0.1
kassko/symfony-bridge ~0.1

by kassko

class resolver factory dependency injection

02/11 2014

0.2.0-alpha.3

0.2.0.0-alpha3

class-resolver integrated to Symfony.

Sources Download

The Requires

php >=5.5.0
symfony/framework-bundle ~2.5
kassko/class-resolver ~0.1@alpha
kassko/common ~0.1
kassko/symfony-bridge ~0.1

by kassko

class resolver factory dependency injection

27/10 2014

0.2.0-alpha.2

0.2.0.0-alpha2

class-resolver integrated to Symfony.

Sources Download

The Requires

by kassko

class resolver factory dependency injection

14/09 2014

0.1.2-alpha

0.1.2.0-alpha

class-resolver integrated to Symfony.

Sources Download

The Requires

class resolver factory dependency injection

14/09 2014

0.1.1-alpha

0.1.1.0-alpha

class-resolver integrated to Symfony.

Sources Download

The Requires

class resolver factory dependency injection

14/09 2014

0.1.0-alpha

0.1.0.0-alpha

class-resolver integrated to Symfony.

Sources Download

The Requires

class resolver factory dependency injection

library class-resolver-bundle

Integrate the class-resolver component to Symfony

kassko/class-resolver-bundle

The README.md

class-resolver-bundle

Installation

There are two differents ways to use the class-resolver

Example of semantic configuration

You can define some class resolvers in semantic configuration and use them in you service configuration file

You can both define some class resolvers on the fly and feed them with pairs [class, service] all from your service configuration file

Finally, you can use some class resolvers defined on the semantic configuration and feed them from your service configuration file

The Versions

dev-kassko-try

The Requires

The Development Requires

by kassko

dev-master

The Requires

The Development Requires

by kassko

v0.3.3.0

The Requires

The Development Requires

by kassko

dev-kassko-new_resolvers

The Requires

The Development Requires

by kassko

v0.3.2.0

The Requires

The Development Requires

by kassko

v0.3.1.0

The Requires

The Development Requires

by kassko

v0.3.0.1-alpha

The Requires

The Development Requires

by kassko

v0.3.0.0-alpha

The Requires

The Development Requires

by kassko

0.2.0-alpha.8

The Requires

The Development Requires

by kassko

0.2.0-alpha.7

The Requires

The Development Requires

by kassko

0.2.0-alpha.6

The Requires

by kassko

0.2.0-alpha.5

The Requires

by kassko

0.2.0-alpha.4

The Requires

by kassko

0.2.0-alpha.3

The Requires

by kassko

0.2.0-alpha.2

The Requires

by kassko

0.1.2-alpha

The Requires

0.1.1-alpha

The Requires

0.1.0-alpha

The Requires