Download the PHP package cjsaylor/libdomain without Composer
On this page you can find all versions of the php package cjsaylor/libdomain. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download cjsaylor/libdomain
More information about cjsaylor/libdomain
Files in cjsaylor/libdomain
Package libdomain
Short Description PHP classes and traits to facilitate domain driven design.
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package libdomain
libdomain
Libdomain is a php library to facilitate domain driven development.
Core concepts
This library contains the following abstract classes:
Entity- An entity is an identifiable object.ValueObject- An object who's values are immutable.Collection- A collection ofEntityobjects.CollectionEntity- An entity object that also acts as a collection (an identifiable collection).
In cases where the abstract classes can't be extended, all functionality of the abstract classes are provided
with traits. For example, if you wanted an existing entity to have the properties of a ValueObject, then you would
use the ReadAccessable trait:
The ConcreteEntity would now be an immutable value object.
Examples
Entity Example
The first example illustrates a user object that accepts an email attribute that must be an immutable email value object.
CollectionEntity example
This next example will illustrate a group of users where that group also has an identity.
Here we will make use of the CollectionEntity which is both a Collection and an Entity.
It will make use of the User entity defined in the first example.
Setter callback example
Let's modify the User object with some custom setter callbacks (available in 1.0.1).
This allows us to typehint (and do other custom set logic for the Email value object).
Concrete entities example
In some instances, we don't want extra properties to be set on our entities. To limit the properties
that can be set on an entity, the PropertyLimitable interface/trait can be implemented:
