README

This free as in freedom component easy up locator generation based on configuration files. Out of the box, it creates locator from an array configuration file and from propel1 schema.xml files.

It is using the php code generator component as a robust base for code generation.

The build status of the current master branch is tracked by Travis CI:

The scrutinizer status are: |

The versioneye status is:

Downloads:

It is also available at openhub.net.

Why

don't like "serviceLocator->get('foo')" (inexplicit API) calls
like the configurable approach of some service locators out there
inspired by a php usergroup presentation called "the flipside of dependency injection" i'Ve seen "i'm not alone"
generated code is easy debug- and understandable (no magic inside)

How

a task specific configuration assembler creates a unified configuration object
unified configuration object is injected into the locator generator
the locator generator creates needed files
a file exists strategy can take care how to deal with existing files

Install

By Hand

mkdir -p vendor/net_bazzline/php_component_locator_generator
cd vendor/net_bazzline/php_component_locator_generator
git clone https://github.com/bazzline/php_component_locator_generator

With Packagist

composer require net_bazzline/php_component_locator_generator:dev-master

Example

Array Configuration File

Take a Look to configuration file.

How To Create

cd <component root directory>
./execute_example ArrayConfiguration
ls data/
vim data/FromArrayConfigurationFileLocator.php

Generated Code

<?php
/**
 * @author Net\Bazzline\Component\Locator
 * @since 2014-06-07
 */

namespace Application\Service;

use My\OtherInterface as MyInterface;
use Application\Locator\BaseLocator as BaseLocator;

/**
 * Class FromArrayConfigurationFileLocator
 *
 * @package Application\Service
 */
class FromArrayConfigurationFileLocator extends BaseLocator implements \My\Full\QualifiedInterface, MyInterface
{
    /**
     * @var $factoryInstancePool
     */
    private $factoryInstancePool = array();

    /**
     * @var $sharedInstancePool
     */
    private $sharedInstancePool = array();

    /**
     * @return \Application\Model\ExampleUniqueInvokableInstance
     */
    public function getExampleUniqueInvokableInstance()
    {
        return new \Application\Model\ExampleUniqueInvokableInstance();
    }

    /**
     * @return \Application\Factory\ExampleUniqueFactorizedInstanceFactory
     */
    public function getExampleUniqueFactorizedInstance()
    {
        return $this->fetchFromFactoryInstancePool('\Application\Factory\ExampleUniqueFactorizedInstanceFactory')->create();
    }

    /**
     * @return \Application\Model\ExampleSharedInvokableInstance
     */
    public function getExampleSharedInvokableInstance()
    {
        return $this->fetchFromSharedInstancePool('\Application\Model\ExampleSharedInvokableInstance');
    }

    /**
     * @return \Application\Factory\ExampleSharedFactorizedInstanceFactory
     */
    public function getExampleSharedFactorizedInstance()
    {
        $className = '\Application\Factory\ExampleSharedFactorizedInstanceFactory';

        if ($this->isNotInSharedInstancePool($className)) {
            $factoryClassName = '\Application\Factory\ExampleSharedFactorizedInstanceFactory';
            $factory = $this->fetchFromFactoryInstancePool($factoryClassName);

            $this->addToSharedInstancePool($className, $factory->create());
        }

        return $this->fetchFromSharedInstancePool($className);
    }
    //... code for internal methods
}

The Locator is taking care of the instance pooling.

Behaviour

creates a FactoryInterface file
creates a InvalidArgumentException if a namespace is given

Terms

Assembler
- implements the AssemblerInterface
- implements the way the Configuration is filled with data
MethodBodyBuilder
- implements the MethodBodyBuilderInterface
- provides a way to extend a instance creation method body
- provides a way to extend the method documentation
FileExistsStrategy
- implements the FileExistsStrategyInterface
- provides a way to deal with the fact a generated file exists already

Benefits

on way of calling the locator generator "php bin/generate_locator "
assembler, method builder and file exists strategy are configuration based runtime variables
highly configurable
- each configuration file needs to be a simple php array
- mandatory array keys are
  - assembler
  - file_exists_strategy
- optional array key is
  - boostrap_file
- rest of configuration is based on the given assembler
shipped with two assembler implementations
- FromArrayAssembler
  - mandatory array keys
    - class_name
    - file_path
  - optional array keys
    - extends (can be empty)
    - implements (can be empty)
    - instances (can be empty)
      - alias
      - is_factory
      - is_shared
      - method_body_builder
    - method_prefix
    - namespace (can be empty)
    - uses (can be empty)
      - alias
- FromPropelSchemaXmlAssembler
  - mandatory array keys
    - class_name
    - file_path
  - optional array keys
    - extends (can be empty)
    - implements (can be empty)
    - method_prefix
    - namespace (can be empty)
    - path_to_schema_xml
    - uses (can be empty)
- implement the AssemblerInterface to write your own assembler
shipped with two file exists strategies
- DeleteStrategy
- SuffixWithCurrentTimestampStrategy
- implement the FileExistsStrategyInterface to write your own strategy
shipped with five method body builder implementations
- FetchFromFactoryInstancePoolBuilder used internally by the generated locator
- FetchFromSharedInstancePoolBuilder used internally by the generated locator
- FetchFromSharedInstancePoolOrCreateByFactoryBuilder used internally by the generated locator
- NewInstanceBuilder used internally by the generated locator
- PropelQueryCreateBuilder as an example to use your own method body builder
- ValidatedInstanceCreationBuilder as an additional example how to use the power of the method body builder support to generate own instance creation code
- implement the MethodBodyBuilderInterface to write your own method body builder
uses separate component for php code generation

API

The API is available at www.bazzline.net, thanks to apigen and the api document builder.

History

upcomming
- @todo
  - added unit test for
    - Command
    - Configuration/Validator/*
    - Generator
    - Process/*
  - add "default" section in the configuration for "is_shared" and "is_factory" (and maybe more)
  - add "verify" method to configuration that throws an error if not all mandatory parameters are set
  - implement validation of used interface- or class names by adding "autoloader class path"
  - implement a flag to create a LocatorInterface out of the written Locator
  - implement "FromPath" assembler that scans the path and iterates through the path and fetches the php class or interfaces
  - split readme into multiple files
  - use "net_bazzline/php_component_cli_environment" to create "net_bazzline_generate_locator"
  - use "net_bazzline/php_component_cli_environment" to create "net_bazzline_generate_locator_configuration <Array|PropelSchemaXml|PropelWithNamespaceSchemaXml> "
- added php 7 continous integration run for travis
- moved to psr-4 autoloading
- updated dependencies
2.0.9 - released at 22.03.2016
- updated dependencies
2.0.8 - released at 11.12.2015
- updated dependencies
2.0.7 - released at 01.12.2015
- updated dependencies
2.0.6 - released at 29.11.2015
- fixed issue 6
- fixed issue 7
- move documentation to www.bazzline.net
- updated dependencies
2.0.5 - released at 18.11.2015
- updated depenceny
2.0.4 - released at 19.09.2015
- updated depenceny
2.0.3 - released at 18.09.2015
- updated depenceny
2.0.2 - released at 28.08.2015
- updated depenceny
2.0.1 - released at 04.07.2015
- updated depenceny
2.0.0 - released at 03.06.2015
- Generator.php now throws "InvalidArgumentException" instead of "RuntimeException
- Generator now tries to create the provided directory if it does not exists
- fixed issue/2
- fixed issue/4
- fixed issue/5
- implement usage of php_component_cli_arguments
- implement usage of php_component_command
- renamed "bin/generalte_locator" to "bin/net_bazzline_generate_locator"
1.5.1 - released at 27.05.2015
- fixed broken entry of "bin" in composer.json
1.5.0 - released at 27.05.2015
- renamed "bin/generateLocator.php" to "bin/generate_locator"
- renamed "example/[..]/run.php" to "example/[...]/run"
- fixed issue 3
1.4.2 - released at 22.05.2015
- updated dependencies
1.4.1 - released at 08.02.2015
- removed dependency to apigen
1.4.0 - released at 07.02.2015
- implemented generation of "LocatorGeneratorInterface"
- easy up usage of examples by adding command "execute_example"
- added example for "method_name_without_namespace"
- updated api
- updated dependencies
1.3.1 - released at 07.02.2015
- easy up usage of examples (by adding a "run.php" in the directories
- updated api
- updated dependencies
1.3.0 - released at 22.12.2014
- implemented "method_name_without_namespace" option in "FromPropelSchemaXmlAssembler" ("createMyTable" instead of "createMyNamespaceMyTable")
1.2.1 - released at 21.12.2014
- updated api
- refactored Command
- refactored FromArrayAssembler
- refactored FromPropelSchemaXmlAssembler
1.2.0 - released at 20.12.2014
- fixed bug in propel name space FromPropelSchemaXmlAssembler
- refactored FromPropelSchemaXmlAssembler
- extended usage output
1.1.0 - released at 13.09.2014
- enhanced Command
  - absolute configuration paths are now supported
- fixed (stupid) broken unittest
- fixed error in Command
  - check if "bootstrap_file" exists in configuration was not well implemented
- updated dependencies
1.0.1 - released at 03.09.2014
- added api
- fixed broken links
- adapted composer.json project name
- moved command logic into simple Command class
- added check in "generateLocator.php" to validate if installed as composer component or not
1.0.0 - released at 31.08.2014
- initial project start
- unit tests
- examples
- codebase itself
- api description

net_bazzline / php_component_locator_generator

Maintainers

Details