symfony / var-exporter
Allows exporting any serializable PHP data structure to plain PHP code
Fund package maintenance!
fabpot
Tidelift
symfony.com/sponsor
Requires
- php: >=8.2
Requires (Dev)
- symfony/property-access: ^6.4|^7.0
- symfony/serializer: ^6.4|^7.0
- symfony/var-dumper: ^6.4|^7.0
- 7.3.x-dev
- 7.2.x-dev
- v7.2.0
- v7.2.0-RC1
- v7.2.0-BETA1
- 7.1.x-dev
- v7.1.6
- v7.1.2
- v7.1.1
- v7.1.0
- v7.1.0-RC1
- v7.1.0-BETA1
- 7.0.x-dev
- v7.0.9
- v7.0.8
- v7.0.7
- v7.0.6
- v7.0.4
- v7.0.3
- v7.0.2
- v7.0.1
- v7.0.0
- v7.0.0-RC2
- v7.0.0-RC1
- v7.0.0-BETA1
- 6.4.x-dev
- v6.4.13
- v6.4.9
- v6.4.8
- v6.4.7
- v6.4.6
- v6.4.4
- v6.4.3
- v6.4.2
- v6.4.1
- v6.4.0
- v6.4.0-RC2
- v6.4.0-RC1
- v6.4.0-BETA1
- 6.3.x-dev
- v6.3.12
- v6.3.11
- v6.3.10
- v6.3.9
- v6.3.6
- v6.3.4
- v6.3.2
- v6.3.0
- v6.3.0-RC1
- v6.3.0-BETA1
- 6.2.x-dev
- v6.2.13
- v6.2.10
- v6.2.8
- v6.2.7
- v6.2.5
- v6.2.3
- v6.2.2
- v6.2.1
- v6.2.0
- v6.2.0-RC1
- v6.2.0-BETA3
- v6.2.0-BETA1
- 6.1.x-dev
- v6.1.11
- v6.1.9
- v6.1.3
- v6.1.1
- v6.1.0
- v6.1.0-RC1
- v6.1.0-BETA2
- v6.1.0-BETA1
- 6.0.x-dev
- v6.0.19
- v6.0.17
- v6.0.10
- v6.0.9
- v6.0.8
- v6.0.7
- v6.0.6
- v6.0.3
- v6.0.0
- v6.0.0-RC1
- v6.0.0-BETA3
- v6.0.0-BETA1
- 5.4.x-dev
- v5.4.45
- v5.4.40
- v5.4.39
- v5.4.35
- v5.4.32
- v5.4.26
- v5.4.21
- v5.4.19
- v5.4.17
- v5.4.10
- v5.4.9
- v5.4.8
- v5.4.7
- v5.4.6
- v5.4.3
- v5.4.2
- v5.4.0
- v5.4.0-RC1
- v5.4.0-BETA3
- v5.4.0-BETA1
- 5.3.x-dev
- v5.3.14
- v5.3.11
- v5.3.8
- v5.3.7
- v5.3.4
- v5.3.3
- v5.3.2
- v5.3.0
- v5.3.0-RC1
- v5.3.0-BETA3
- v5.3.0-BETA1
- 5.2.x-dev
- v5.2.12
- v5.2.11
- v5.2.10
- v5.2.8
- v5.2.7
- v5.2.4
- v5.2.3
- v5.2.2
- v5.2.1
- v5.2.0
- v5.2.0-RC2
- v5.2.0-RC1
- v5.2.0-BETA3
- v5.2.0-BETA2
- v5.2.0-BETA1
- 5.1.x-dev
- v5.1.11
- v5.1.10
- v5.1.9
- v5.1.8
- v5.1.7
- v5.1.6
- v5.1.5
- v5.1.4
- v5.1.3
- v5.1.2
- v5.1.1
- v5.1.0
- v5.1.0-RC2
- v5.1.0-RC1
- v5.1.0-BETA1
- 5.0.x-dev
- v5.0.11
- v5.0.10
- v5.0.9
- v5.0.8
- v5.0.7
- v5.0.6
- v5.0.5
- v5.0.4
- v5.0.3
- v5.0.2
- v5.0.1
- v5.0.0
- v5.0.0-RC1
- v5.0.0-BETA2
- v5.0.0-BETA1
- 4.4.x-dev
- v4.4.43
- v4.4.42
- v4.4.41
- v4.4.40
- v4.4.39
- v4.4.37
- v4.4.34
- v4.4.31
- v4.4.30
- v4.4.27
- v4.4.26
- v4.4.25
- v4.4.23
- v4.4.22
- v4.4.20
- v4.4.19
- v4.4.18
- v4.4.17
- v4.4.16
- v4.4.15
- v4.4.14
- v4.4.13
- v4.4.12
- v4.4.11
- v4.4.10
- v4.4.9
- v4.4.8
- v4.4.7
- v4.4.6
- v4.4.5
- v4.4.4
- v4.4.3
- v4.4.2
- v4.4.1
- v4.4.0
- v4.4.0-RC1
- v4.4.0-BETA2
- v4.4.0-BETA1
- 4.3.x-dev
- v4.3.11
- v4.3.10
- v4.3.9
- v4.3.8
- v4.3.7
- v4.3.6
- v4.3.5
- v4.3.4
- v4.3.3
- v4.3.2
- v4.3.1
- v4.3.0
- v4.3.0-RC1
- v4.3.0-BETA2
- v4.3.0-BETA1
- 4.2.x-dev
- v4.2.12
- v4.2.11
- v4.2.10
- v4.2.9
- v4.2.8
- v4.2.7
- v4.2.6
- v4.2.5
- v4.2.4
- v4.2.3
- v4.2.2
- v4.2.1
- v4.2.0
- v4.2.0-RC1
- v4.2.0-BETA2
- v4.2.0-BETA1
This package is auto-updated.
Last update: 2024-11-29 09:10:46 UTC
README
The VarExporter component provides various tools to deal with the internal state of objects:
VarExporter::export()
allows exporting any serializable PHP data structure to plain PHP code. While doing so, it preserves all the semantics associated with the serialization mechanism of PHP (__wakeup
,__sleep
,Serializable
,__serialize
,__unserialize
);Instantiator::instantiate()
creates an object and sets its properties without calling its constructor nor any other methods;Hydrator::hydrate()
can set the properties of an existing object;Lazy*Trait
can make a class behave as a lazy-loading ghost or virtual proxy.
VarExporter::export()
The reason to use VarExporter::export()
vs serialize()
or
igbinary is performance: thanks to
OPcache, the resulting code is significantly faster and more memory efficient
than using unserialize()
or igbinary_unserialize()
.
Unlike var_export()
, this works on any serializable PHP value.
It also provides a few improvements over var_export()
/serialize()
:
- the output is PSR-2 compatible;
- the output can be re-indented without messing up with
\r
or\n
in the data; - missing classes throw a
ClassNotFoundException
instead of being unserialized toPHP_Incomplete_Class
objects; - references involving
SplObjectStorage
,ArrayObject
orArrayIterator
instances are preserved; Reflection*
,IteratorIterator
andRecursiveIteratorIterator
classes throw an exception when being serialized (their unserialized version is broken anyway, see https://bugs.php.net/76737).
Instantiator and Hydrator
Instantiator::instantiate($class)
creates an object of the given class without
calling its constructor nor any other methods.
Hydrator::hydrate()
sets the properties of an existing object, including
private and protected ones. For example:
// Sets the public or protected $object->propertyName property Hydrator::hydrate($object, ['propertyName' => $propertyValue]); // Sets a private property defined on its parent Bar class: Hydrator::hydrate($object, ["\0Bar\0privateBarProperty" => $propertyValue]); // Alternative way to set the private $object->privateBarProperty property Hydrator::hydrate($object, [], [ Bar::class => ['privateBarProperty' => $propertyValue], ]);
Lazy*Trait
The component provides two lazy-loading patterns: ghost objects and virtual proxies (see https://martinfowler.com/eaaCatalog/lazyLoad.html for reference).
Ghost objects work only with concrete and non-internal classes. In the generic case, they are not compatible with using factories in their initializer.
Virtual proxies work with concrete, abstract or internal classes. They provide an API that looks like the actual objects and forward calls to them. They can cause identity problems because proxies might not be seen as equivalents to the actual objects they proxy.
Because of this identity problem, ghost objects should be preferred when
possible. Exceptions thrown by the ProxyHelper
class can help decide when it
can be used or not.
Ghost objects and virtual proxies both provide implementations for the
LazyObjectInterface
which allows resetting them to their initial state or to
forcibly initialize them when needed. Note that resetting a ghost object skips
its read-only properties. You should use a virtual proxy to reset read-only
properties.
LazyGhostTrait
By using LazyGhostTrait
either directly in your classes or by using
ProxyHelper::generateLazyGhost()
, you can make their instances lazy-loadable.
This works by creating these instances empty and by computing their state only
when accessing a property.
class FooLazyGhost extends Foo { use LazyGhostTrait; } $foo = FooLazyGhost::createLazyGhost(initializer: function (Foo $instance): void { // [...] Use whatever heavy logic you need here // to compute the $dependencies of the $instance $instance->__construct(...$dependencies); // [...] Call setters, etc. if needed }); // $foo is now a lazy-loading ghost object. The initializer will // be called only when and if a *property* is accessed.
LazyProxyTrait
Alternatively, LazyProxyTrait
can be used to create virtual proxies:
$proxyCode = ProxyHelper::generateLazyProxy(new ReflectionClass(Foo::class)); // $proxyCode contains the reference to LazyProxyTrait // and should be dumped into a file in production envs eval('class FooLazyProxy'.$proxyCode); $foo = FooLazyProxy::createLazyProxy(initializer: function (): Foo { // [...] Use whatever heavy logic you need here // to compute the $dependencies of the $instance $instance = new Foo(...$dependencies); // [...] Call setters, etc. if needed return $instance; }); // $foo is now a lazy-loading virtual proxy object. The initializer will // be called only when and if a *method* is called.