Download the PHP package brick/varexporter without Composer

Brick\VarExporter

A powerful and pretty replacement for PHP's var_export().

Introduction

PHP's var_export() function is a handy way to export a variable as executable PHP code.

It is particularly useful to store data that can be cached by OPCache, just like your source code, and later retrieved very fast, much faster than unserializing data using unserialize() or json_decode().

But it also suffers from several drawbacks:

• It cannot export custom objects that do not implement __set_state(), and __set_state() does not play well with private properties in parent classes, which makes the implementation tedious
• It does not support closures

Additionally, the output is not very pretty:

• It outputs arrays as array() notation, instead of the short [] notation
• It outputs numeric arrays with explicit and unnecessary 0 => ... key => value syntax

This library aims to provide a prettier, safer, and powerful alternative to var_export().
The output is valid and standalone PHP code, that does not depend on the brick/varexporter library.

Installation

This library is installable via Composer:

Requirements

This library requires PHP 7.4 or later.

For PHP 7.2 & 7.3 compatibility, you can use version 0.3. For PHP 7.1, you can use version 0.2. Note that these PHP versions are EOL and not supported anymore. If you're still using one of these PHP versions, you should consider upgrading as soon as possible.

Project status & release process

While this library is still under development, it is well tested and should be stable enough to use in production environments.

The current releases are numbered 0.x.y. When a non-breaking change is introduced (adding new methods, optimizing existing code, etc.), y is incremented.

When a breaking change is introduced, a new 0.x version cycle is always started.

It is therefore safe to lock your project to a given release cycle, such as 0.5.*.

If you need to upgrade to a newer release cycle, check the release history for a list of changes introduced by each further 0.x.0 version.

Quickstart

This library offers a single method, VarExporter::export() which works pretty much like var_export():

This code will output:

Compare this to the var_export() output:

Note: unlike var_export(), export() always returns the exported variable, and never outputs it.

Exporting custom objects

var_export() assumes that every object has a static __set_state() method that takes an associative array of property names to values, and returns a object.

This means that if you want to export an instance of a class outside your control, you're screwed up. This also means that you have to write boilerplate code for your classes, that looks like:

Or the more dynamic, reusable, and less IDE-friendly version:

If your class has a parent with private properties, you may have to do some gymnastics to write the value, and if your class overrides a private property of one of its parents, you're out of luck as var_export() puts all properties in the same bag, outputting an array with a duplicate key.

What does VarExporter do instead?

It determines the most appropriate method to export your object, in this order:

• If your custom class has a __set_state() method, VarExporter uses it by default, just like var_export() would do:

  The array passed to __set_state() will be built with the same semantics used by var_export(); this library aims to be 100% compatible in this regard. The only difference is when your class has overridden private properties: var_export() will output an array that contains the same key twice (resulting in data loss), while VarExporter will throw an ExportException to keep you on the safe side.

  Unlike var_export(), this method will only be used if actually implemented on the class.

  You can disable exporting objects this way, even if they implement __set_state(), using the NO_SET_STATE option.

• If your class has __serialize() and __unserialize() methods, VarExporter uses the output of __serialize() to export the object, and gives it as input to __unserialize() to reconstruct the object:

  This method is recommended for exporting complex custom objects: it is forward compatible with the new serialization mechanism introduced in PHP 7.4, flexible, safe, and composes very well under inheritance.

  If for any reason you do not want to export objects that implement __serialize() and __unserialize() using this method, you can opt out by using the NO_SERIALIZE option.

• If the class does not meet any of the conditions above, it is exported through direct property access, which in its simplest form looks like:

  If the class has a constructor, it will be bypassed using reflection:

  If the class has non-public properties, they will be accessed through closures bound to the object:

  You can disable exporting objects this way, using the NOT_ANY_OBJECT option.

If you attempt to export a custom object and all compatible exporters have been disabled, an ExportException will be thrown.

Exporting closures

Since version 0.2.0, VarExporter has experimental support for closures:

To do this magic, VarExporter parses the PHP source file where your closure is defined, using the well-established nikic/php-parser library, inspired by SuperClosure.

To ensure that the closure will work in any context, it rewrites its source code, replacing any namespaced class/function/constant name with its fully qualified counterpart:

Note how all namespaced classes, and explicitly namespaced functions and constants, have been rewritten, while the non-namespaced function strlen() and the non-namespaced constant have been left as is. Please see the first caveat.

Use statements

By default, exporting closures that have variables bound through use() will throw an ExportException. This is intentional, because exported closures can be executed in another context, and as such must not rely on the context they've been originally defined in.

When using the CLOSURE_SNAPSHOT_USES option, VarExporter will export the current value of each use() variable instead of throwing an exception. The exported variables are added as expression inside the exported closure.

Arrow functions

PHP supports shorthand syntax for closures (since PHP 7.4), also known as arrow functions. VarExporter will export these as normal closures.

Arrow functions can implicitly use variables from the context they've been defined in. If any context variable is used in the arrow function, VarExporter will throw an ExportException unless the CLOSURE_SNAPSHOT_USES option is used.

Caveats

• Functions and constants that are not explicitly namespaced, either directly or through a use function or use const statement, are always exported as is. This is because the parser does not have the runtime context to check if a definition for this function or constant exists in the current namespace, and as such cannot reliably predict the behaviour of PHP's fallback to global function/constant. Be really careful here if you're using namespaced functions or constants: always explicitly import your namespaced functions and constants, if any.
• Closures can use $this, but will not be bound to an object once exported. You must explicitly bind them through bindTo() if required, after running the exported code.
• You cannot have 2 closures on the same line in your source file, or an ExportException will be thrown. This is because VarExporter cannot know which one holds the definition for the \Closure object it encountered.
• Closures defined in eval()'d code cannot be exported and throw an ExportException, because there is no source file to parse.

You can disable exporting closures, using the NO_CLOSURES option. When this option is set, an ExportException will be thrown when attempting to export a closure.

Options

VarExporter::export() accepts a bitmask of options as a second parameter:

Available options:

VarExporter::ADD_RETURN

Wraps the output in a return statement:

This makes the code ready to be executed in a PHP file―or eval(), for that matter.

VarExporter::ADD_TYPE_HINTS

Adds type hints to objects created through reflection, and to $this inside closures bound to an object. This allows the resulting code to be statically analyzed by external tools and IDEs:

VarExporter::SKIP_DYNAMIC_PROPERTIES

Skips dynamic properties on custom classes in the output. Dynamic properties are properties that are not part of the class definition, and added to an object at runtime. By default, any dynamic property set on a custom class is exported; if this option is used, dynamic properties are only allowed on stdClass objects, and ignored on other objects.

VarExporter::NO_SET_STATE

Disallows exporting objects through __set_state().

VarExporter::NO_SERIALIZE

Disallows exporting objects through __serialize() and __unserialize().

VarExporter::NOT_ANY_OBJECT

Disallows exporting any custom object using direct property access and bound closures.

VarExporter::NO_CLOSURES

Disallows exporting closures.

VarExporter::INLINE_ARRAY

Formats arrays on a single line:

VarExporter::INLINE_SCALAR_LIST

Formats numeric arrays containing only scalar values on a single line:

Types considered scalar here are int, bool, float, string and null.

This option is a subset of INLINE_ARRAY, and has no effect when INLINE_ARRAY is used.

VarExporter::TRAILING_COMMA_IN_ARRAY

Adds a trailing comma after the last item of non-inline arrays:

VarExporter::CLOSURE_SNAPSHOT_USES

Export the current value of each use() variable as expression inside the exported closure.

Indentation

You can use the 3rd argument of VarExporter::export() to control the indentation level. This is useful when you want to use the generated code string to replace a placeholder in a template used to generate code files.

So using output of VarExporter::export(['foo' => 'bar'], indentLevel: 1) in the template below to replace {{exported}}:

would result in:

Note that the first line will never be indented, as we can see in the example above.

Error handling

Any error occurring on export() will throw an ExportException:

Limitations

• Exporting internal classes other than stdClass and Closure, and classes implementing __set_state() (most notably DateTime classes) is currently not supported. VarExporter will throw an ExportException if it finds one.

  To avoid hitting this brick wall, you can implement __serialize() and __unserialize() in classes that contain references to internal objects.

  Feel free to open an issue or a pull request if you think that an internal class could/should be exportable.

• Exporting anonymous classes is not supported yet. Ideas or pull requests welcome.

• Just like var_export(), VarExporter cannot currently maintain object identity (two instances of the same object, once exported, will create two equal (==) yet distinct (!==) objects).

• And just like var_export(), it cannot currently handle circular references, such as object A pointing to B, and B pointing back to A.

In pretty much every other case, it offers an elegant and very efficient way to cache data to PHP files, and a solid alternative to serialization.