.. index:: single: Yaml single: Components; Yaml
The Yaml component loads and dumps YAML files.
The Symfony Yaml component parses YAML strings to convert them to PHP arrays. It is also able to convert PHP arrays to YAML strings.
YAML, YAML Ain't Markup Language, is a human friendly data serialization standard for all programming languages. YAML is a great format for your configuration files. YAML files are as expressive as XML files and as readable as INI files.
The Symfony Yaml Component implements a selected subset of features defined in the YAML 1.2 version specification.
Tip
Learn more about the Yaml component in the :doc:`/components/yaml/yaml_format` article.
You can install the component in 2 different ways:
- :doc:`Install it via Composer </components/using_components>` (
symfony/yaml
on Packagist); - Use the official Git repository (https://github.com/symfony/yaml).
One of the goals of Symfony Yaml is to find the right balance between speed and features. It supports just the needed features to handle configuration files. Notable lacking features are: document directives, multi-line quoted messages, compact block collections and multi-document files.
It sports a real parser and is able to parse a large subset of the YAML specification, for all your configuration needs. It also means that the parser is pretty robust, easy to understand, and simple enough to extend.
Whenever you have a syntax problem with your YAML files, the library outputs a helpful message with the filename and the line number where the problem occurred. It eases the debugging a lot.
It is also able to dump PHP arrays to YAML with object support, and inline level configuration for pretty outputs.
It supports most of the YAML built-in types like dates, integers, octals, booleans, and much more...
Full support for references, aliases, and full merge key. Don't repeat yourself by referencing common configuration bits.
The Symfony Yaml component is very simple and consists of two main classes: one parses YAML strings (:class:`Symfony\\Component\\Yaml\\Parser`), and the other dumps a PHP array to a YAML string (:class:`Symfony\\Component\\Yaml\\Dumper`).
On top of these two classes, the :class:`Symfony\\Component\\Yaml\\Yaml` class acts as a thin wrapper that simplifies common uses.
The :method:`Symfony\\Component\\Yaml\\Yaml::parse` method parses a YAML string and converts it to a PHP array:
use Symfony\Component\Yaml\Yaml;
$value = Yaml::parse(file_get_contents('/path/to/file.yml'));
Caution!
Because it is currently possible to pass a filename to this method, you must validate the input first. Passing a filename is deprecated in Symfony 2.2, and was removed in Symfony 3.0.
If an error occurs during parsing, the parser throws a :class:`Symfony\\Component\\Yaml\\Exception\\ParseException` exception indicating the error type and the line in the original YAML string where the error occurred:
use Symfony\Component\Yaml\Exception\ParseException;
try {
$value = Yaml::parse(file_get_contents('/path/to/file.yml'));
} catch (ParseException $e) {
printf("Unable to parse the YAML string: %s", $e->getMessage());
}
.. versionadded:: 2.7 Support for parsing mappings as objects was introduced in Symfony 2.7.
Yaml :ref:`mappings <yaml-format-collections>` are basically associative
arrays. You can instruct the parser to return mappings as objects (i.e.
\stdClass
instances) by setting the fourth argument to true
:
$object = Yaml::parse('{"foo": "bar"}', false, false, true); echo get_class($object); // stdClass echo $object->foo; // bar
The :method:`Symfony\\Component\\Yaml\\Yaml::dump` method dumps any PHP array to its YAML representation:
use Symfony\Component\Yaml\Yaml;
$array = array(
'foo' => 'bar',
'bar' => array('foo' => 'bar', 'bar' => 'baz'),
);
$yaml = Yaml::dump($array);
file_put_contents('/path/to/file.yml', $yaml);
If an error occurs during the dump, the parser throws a :class:`Symfony\\Component\\Yaml\\Exception\\DumpException` exception.
The YAML format supports two kind of representation for arrays, the expanded one, and the inline one. By default, the dumper uses the expanded representation:
foo: bar
bar:
foo: bar
bar: baz
The second argument of the :method:`Symfony\\Component\\Yaml\\Yaml::dump` method customizes the level at which the output switches from the expanded representation to the inline one:
echo Yaml::dump($array, 1);
foo: bar
bar: { foo: bar, bar: baz }
echo Yaml::dump($array, 2);
foo: bar
bar:
foo: bar
bar: baz
By default the YAML component will use 4 spaces for indentation. This can be changed using the third argument as follows:
// use 8 spaces for indentation echo Yaml::dump($array, 2, 8);
foo: bar
bar:
foo: bar
bar: baz
By default the YAML component will encode any "unsupported" type (i.e.
resources and objects) as null
.
Instead of encoding as null
you can choose to throw an exception if an invalid
type is encountered in either the dumper or parser as follows:
// throw an exception if a resource or object is encountered Yaml::dump($data, 2, 4, true); // throw an exception if an encoded object is found in the YAML string Yaml::parse($yaml, true);
However, you can activate object support using the next argument:
$object = new \stdClass(); $object->foo = 'bar'; $dumped = Yaml::dump($object, 2, 4, false, true); // !!php/object:O:8:"stdClass":1:{s:5:"foo";s:7:"bar";} $parsed = Yaml::parse($dumped, false, true); var_dump(is_object($parsed)); // true echo $parsed->foo; // bar
The YAML component uses PHP's serialize()
method to generate a string
representation of the object.
Caution!
Object serialization is specific to this implementation, other PHP YAML
parsers will likely not recognize the php/object
tag and non-PHP
implementations certainly won't - use with discretion!
.. toctree:: :maxdepth: 1 :glob: yaml/*