Installer for all the Hostnet Doctrine entity libraries
This package is auto-updated.
Last update: 2020-02-21 10:08:41 UTC
The Hostnet Entity Composer plugin was developed to solve several problems experienced with plain usage of the Doctrine ORM. Although our solution is inspired on working with doctrine it is perfectly usable for every other way of persisting entities. The problems we came across are:
- Entities became really big;
- Entities were shared between applications and these applications inherited functionality they were not allowed to use;
- Knowledge areas like calculating discounts were spread through the model and not grouped together;
- Misuse of inheritance to prevent code duplication.
To solve our problem we borrowed some ideas from another realm of software development, since we felt we were hitting the boundaries of Object Oriented Programming and sought for more modularization. We used the ideas behind Aspect Oriented Programming to solve our problems.
The basic concept: Entities are grouped by responsibility in packages. This plugin links the packages together.
This is awesome for you if;
- You maintain an open source project that includes entities, that you would like people to expand on.
- You have a database and various applications accessing different (but related) subsets of that database.
- Or searching to glue something yourself.
If you do not belong in one of those groups, be careful since this might not be what you want.
One application needs to know about
Clients, but is unaware of the concept of a
Contract. Another application requires access to both of them. So in one application, you'd want to be able to call
$client->getContracts(). But in the other, you'd prefer to not know about contracts at all!
With this plugin you can create one package that is purely
Client focussed, and another that is
Contract focussed, and that injects the additional functionality (like
- Create a composer package to put your entities in.
- Use PSR-0 or PSR-4 autoloading for the src/ directory.
- The package should be of type
- The package should require
- Create one entity, say
Page, inside a namespace that ends with
php composer.phar dump-autoload. (The entity plugin hooks to this event.) This should cause some output:
Pass 1/3: Generating compound traits and interfaces Pass 2/3: Preparing individual generation Pass 3/3: Performing individual generation
- From your entity, use the trait generated in the
Congratulations, you now have an extendable entity package.
Follow the steps above, and
- Make sure your new package depends on the old one.
- Instead of creating the
Pageclass, create a
php composer.phar update.
vendor/your-vendor-name/your-package-name/src/Entity/Generated/PageTraits.php. It should include a reference to your package.
If you run the composer.phar with
-vvv it will show more information.
If you want to extend an entity from your main application, you can use the
entity-bundle-dir setting in the extra section of your composer.json.
If you do not want to generate interfaces, you can set the
generate-interfaces setting to
false in the extra setting of your composer.json.
We will change this to being the default behaviour in a future release.
For a quick overview have a look at the cheatsheet.