Download the PHP package scn/hydrator without Composer
On this page you can find all versions of the php package scn/hydrator. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Package hydrator
Short Description A pragmatic hydrator and extractor library
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 hydrator
scn/hydrator
A pragmatic hydrator and extractor library
Installation
Via Composer:
Usage
See the examples folder for usage instructions by code.
Extraction
First of all you'll need a class that implements \Scn\Hydrator\Config\ExtractorConfigInterface.
The only method getExtractorProperties has to return an array with string keys and callables as values.
The string keys of this array are used to craft the result of the extraction.
The corresponding callables must have the signature callable(string $propertyName): mixed. The $propertyName
parameter will be the corresponding string key. You will usually not need this information.
If this callable is an instance of \Closure, its' $this and static context are bound to the entity object to
extract. As a result of this the closure will have access to private and protected properties and methods of the entity.
A short example:
Hydration
For hydration you'll need a class implementing \Scn\Hydrator\Configuration\HydratorConfigInterface.
The only method getHydratorProperties has to return an array with string keys and callables as values.
As an alternative you can use the \Scn\Hydrator\Configuration\GenericHydratorConfig.
The string keys have to correspond the keys in the data to hydrate your object with.
The corresponding callables must have the signature callable(mixed $value, string $propertyName): void.
The $propertyName parameter will be the corresponding string key. You will usually not need this information.
If this callable is an instance of \Closure, its' $this and static context are bound to the entity object to
hydrate. As a result of this the closure will have access to private and protected properties and methods of the entity.
A short example:
Hydration flags
The hydrate method has a fourth, optional bit flag parameter $flags.
Currently there are two options available
\Scn\Hydrator\Hydrator::NO_STRICT_KEYS (1)
If this bit is set in $flags, the hydrator will ignore keys in the data array that have no corresponding key in the array
the getHydratorProperties method returns.
This bit is not set by default, additional keys in the data array will lead to an \InvalidArgumentException exception thrown by the hydrator.
\Scn\Hydrator\Hydrator::IGNORE_KEYS (2)
If this bit is set, the hydrator will ignore the keys of the data array but assume the entries in the data array are in the same order as in the hydrator configuration array.
Example:
