Update README.md

README.md

@@ -4,80 +4,7 @@
 [![Scrutinizer Code Quality](https://scrutinizer-ci.com/g/kleijnweb/php-api-hydrator/badges/quality-score.png?b=master)](https://scrutinizer-ci.com/g/kleijnweb/php-api-hydrator/?branch=master)
 [![Latest Stable Version](https://poser.pugx.org/kleijnweb/php-api-hydrator/v/stable)](https://packagist.org/packages/kleijnweb/php-api-hydrator)
 
-A PHP7 library for hydrating objects using [KleijnWeb\PhpApi\Descriptions](https://github.com/kleijnweb/php-api-descriptions).
-
-# Minimal Usage
-
-```php
-// $input is deserialized and validated using $inputSchema
-
-$builder   = new ProcessorBuilder(new ClassNameResolver(['Some\Namespace']));
-$processor = $builder->build($schema);
-$hydrated  = $processor->hydrate($input, $inputSchema);
-
-// Perform business logic, creating $appOutput
-
-$output = $processor->dehydrate($appOutput, $outputSchema);
-
-// Validate output using $outputSchema
-```
-### NULLs, Undefined And Defaults
-
-The processor will assume hydration input is pre-validated. This implies that when an input object contains a property with a NULL value, it will leave it as is, 
-and it may be casted to something other than NULL if the input is invalid (otherwise it will be "hydrated" by `NullProcessor`). 
-When dehydrating, the processors will intentionally *not* try to force validity of anything that may have been set to an invalid value by application processing.
-
-The implied flow is thus: `input > deserialization > validation > hydration > business logic > dehydration [> validation] > serialization > output` .
-
-When adhering to this flow, the behavior should be intuitive. There is a separate document detailing the implementation [here](NULLS.md).
-
-### DateTime
-
-The expected in- and output format can be tweaked by configuring the DateTimeProcessor factory with a custom instance of `DateTimeSerializer` (via the builder):
-
- ```php
-$builder = new ProcessorBuilder($classNameResolver, new DateTimeSerializer(\DateTime::RFC850));
- ```
-
-By default output is formatted as 'Y-m-d\TH:i:s.uP' (RFC3339 with microseconds). When passed, the first constructor argument will be used instead. 
-Input parsing is attempted as follows:
-
-<ol>
-  <li>Arguments to the constructor</li>
-  <li>RFC3339 with decreasing precision:</li>
-  <ol>
-    <li>RFC3339 with microseconds</li>
-    <li>RFC3339 with milliseconds</li>
-    <li>RFC3339</li>
-  </ol>
-  <li>ISO8601</li>
-</ol>
-
-**NOTE**: Formats not starting with `Y-m-d` do not work with Schema::FORMAT_DATE nor `AnyProcessor`. 
-
-### Custom Processors
-
-Class name resolution and DateTime handling can be tweaked by injecting custom instances into the builder, but pretty much all parts of the hydration and dehydration processes are customizable. You can inject custom processors by injecting factories for them into the "processor factory queue". 
-All of the processors and their factories are open for extension. Use cases include:
-
- - Loading objects from a data store
- - Maintaining identity of objects that occur more than once in a structure
- - Custom typed object hydration (eg. using constructors, setters)
- - Custom object creation per type
- - Issuing domain events on object creation
- - Coercing scalar values (eg. interpreting 'false' as FALSE)
- - Pretty much anything else you can think of
-
-Some examples can be found [here](EXAMPLES.md).
-
-### Performance Expectations
-
-On my old Xeon W3570, both hydration and deydration of a an array of 1000 realistic objects (nested objects, arrays) takes about 100ms; 
-on average a little short of 1ms per root object.  
-
-# Contributing
-
-Pull requests are *very* welcome, but the code has to be PSR2 compliant, follow used conventions concerning parameter and return type declarations, and the coverage can not go down. 
+**DEPRECATED:**: This behavior has been integrated into [KleijnWeb\PhpApi\Descriptions](https://github.com/kleijnweb/php-api-descriptions).
 
 ## License