PHPackages                             docdigital/php-class-editor - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. docdigital/php-class-editor

ActiveLibrary[Utility & Helpers](/categories/utility)

docdigital/php-class-editor
===========================

Library to tokenize, edit and override PHP classes

3803[1 issues](https://github.com/juanmf/SourceEditor/issues)PHP

Since Aug 8Pushed 11y ago1 watchersCompare

[ Source](https://github.com/juanmf/SourceEditor)[ Packagist](https://packagist.org/packages/docdigital/php-class-editor)[ RSS](/packages/docdigital-php-class-editor/feed)WikiDiscussions master Synced 3d ago

READMEChangelogDependenciesVersions (1)Used By (0)

SourceEditor
============

[](#sourceeditor)

Library to tokenize, edit and override PHP classes.

Installation
============

[](#installation)

It can be installed with [composer](https://getcomposer.org/doc/00-intro.md) in the CLI. First add the package to your composer.json

```
    "require": {
       ...
        "docdigital/php-class-editor": "dev-master"
    },
```

then update your project

```
$ php composer.phar update docdigital/php-class-editor

```

Or just:

```
$ php composer.phar require docdigital/php-class-editor:dev-master

```

And including the classes in your code:

```
use DocDigital\Lib\SourceEditor\PhpClassEditor;
use DocDigital\Lib\SourceEditor\ClassStructure\ClassElement;
```

You might also need to include composer's [autoload](https://getcomposer.org/doc/04-schema.md#psr-0)

Testing and suggestions are very wellcome.

Overview
========

[](#overview)

Attempts to handle modiffications in existing PHP Class, by adding annotations to specific properties, adding properties and methods.

This is useful for instance to add annotations to an entity Generated by {@link \\Doctrine\\ORM\\Tools\\EntityGenerator}

The Idea is to make is simple to get parts of the code as relevant elements and manipulate them. In the next example I have 3 relevant elements, each having
sub-elements accessible from the main (parent??) one.

```
 /**
  * Class Doc Block
  */
 class a
 {
     /**
      * Attr Doc Block
      */
     public $attr

     /**
      * Fn Doc Block
      */
     public function b()
     {
   }
 }
```

```

```

Then you should be able to issue:

```
    /* @var $classEditor DocDigital\Lib\SourceEditor\PhpClassEditor */
    $classEditor->parseFile($classPath);
    $classEditor->getClass('a')->getMethod('b')->addAnnotation('@auth Juan Manuel Fernandez ');
    $classEditor->getClass('a')->getAttribute('attr')->addAnnotation('@Assert\Choice(...)');
    $classEditor->getClass('a')->addAttribute($attr2);
    $classEditor->getClass('a')->addUse('use DocDigital\Bundle\DocumentBundle\DocumentGenerator\Annotation as DdMapping;');
    $classEditor->getClass('a')->addConst('    const CONSTANT = 1;');
```

When finished you must render the file.

```
    // Element::render() is a composite pattern implementation, class renders its children and so on.
    file_put_contents('PATH/TO/CLASS/FILE', $classEditor->getClass('a')->render(false));
```

to get a reference to the Class representation (ClassElement) you have to do something like this

```
    /**
     * Used to add annotations and validaton methods on generated php classes
     *
     * @var PhpClassEditor
     */
    private $phpClassEditor;

    /**
     * Parses The just writteng PHP Entity and returns a CalssElement representation.
     *
     * @param \DocDigital\Bundle\DocumentBundle\Entity\DocumentType $docDefinition
     *
     * @return DocDigital\Lib\SourceEditor\ClassStructure\ClassElement A class
     * definition representing the Document being Modiffied.
     */
    public function parseDocument(DocumentType $docDefinition)
    {
        $classPath = $this->getDocumentClassPath($docDefinition);
        $classes = $this->phpClassEditor->parseFile($classPath);
        $document = end($classes);
        return $document;
    }
```

In this example Method I add Constants to a Doctrine Entity programatically, to specify ROLES the user must have

```
    /**
     * Adds standar ROLES to this entity, as constants useful to ask consistently
     * for a given ROLE in any Controller or view.
     *
     * @param ClassElement $docDefinition
     * @param DocumentType $docDefinition
     */
    public function addEntityRoles(ClassElement $document, DocumentType $docDefinition)
    {
        $docBlock = "/**\n    * Role required for this Document to perform this action\n    */";
        $document->addConst(
                sprintf('    const ROLE_LIST = \'ROLE_%s_LIST\';', strtoupper($docDefinition->getClassName())),
                $docBlock
            );
        $document->addConst(sprintf('    const ROLE_VIEW = \'ROLE_%s_VIEW\';', strtoupper($docDefinition->getClassName())));
        $document->addConst(sprintf('    const ROLE_EDIT = \'ROLE_%s_EDIT\';', strtoupper($docDefinition->getClassName())));
        $document->addConst(sprintf('    const ROLE_CREATE = \'ROLE_%s_CREATE\';', strtoupper($docDefinition->getClassName())));
        $document->addConst(sprintf('    const ROLE_DELETE = \'ROLE_%s_DELETE\';', strtoupper($docDefinition->getClassName())));
    }
```

the result afer overriding the file is:

```
/**
 * Asd
 *
 * @ORM\Table(name="custom_doc_asd")
 * @ORM\Entity
 */
class Asd extends \DocDigital\Bundle\DocumentBundle\Entity\Document
{

    /**
    * Role required for this Document to perform this action
    */
    const ROLE_LIST = 'ROLE_ASD_LIST';

    /**
     *
     */
    const ROLE_VIEW = 'ROLE_ASD_VIEW';

    /**
     *
     */
    const ROLE_EDIT = 'ROLE_ASD_EDIT';

    /**
     *
     */
    const ROLE_CREATE = 'ROLE_ASD_CREATE';

    /**
     *
     */
    const ROLE_DELETE = 'ROLE_ASD_DELETE';
    ...
```

Internals
=========

[](#internals)

Here's TokenParser.php's DocBlock. The parser is a decoupled piece of code, PhpClassEditor relies on it and gives it 2 Closures to arrange the class composite structure.

```
/**
 * Handles Token classification, code {@link ElementBuilder} creation and code context/scope
 * changes detection. Each ElementBuilder will contain either a significant code part or gap code,
 * like T_WHITESPACE or unclassified code, like method body (as currently not inspecting inside method).
 *
 * Every time an ElementBuilder is closed, or a context changes (which also closes an ElementBuilder)
 * it gets forwarded to a couple of callback closures given by client code:
 *    {@link self::$contextChangeClosure}
 *    {@link self::$processElementClosure}
 *
 * Which are passed as parameters to {@link self::setSource()}
 *
 * The basic sequence is:
 * +------------+  +--------------+
 * | :ClientObj |  | :TokenParser |
 * +------------+  +--------------+
 *      |              |
 *      |--setSource-->|
 *      |--parseCode-->|--readToken--+[forEach Token, this iteration changes context as token is a contextStart]
 *      |              ||