BlueSpice MediaWiki REL1_27
 All Classes Namespaces Files Functions Variables Groups Pages
CHANGELOG

3.4.0

  • added support for parsing YAML files using the Yaml::parseFile() or Parser::parseFile() method
  • the Dumper, Parser, and Yaml classes are marked as final
  • Deprecated the !php/object: tag which will be replaced by the !php/object tag (without the colon) in 4.0.
  • Deprecated the !php/const: tag which will be replaced by the !php/const tag (without the colon) in 4.0.
  • Support for the !str tag is deprecated, use the !!str tag instead.
  • Deprecated using the non-specific tag ! as its behavior will change in 4.0. It will force non-evaluating your values in 4.0. Use plain integers or !!float instead.

3.3.0

  • Starting an unquoted string with a question mark followed by a space is deprecated and will throw a ParseException in Symfony 4.0.
  • Deprecated support for implicitly parsing non-string mapping keys as strings. Mapping keys that are no strings will lead to a ParseException in Symfony 4.0. Use quotes to opt-in for keys to be parsed as strings.

    Before:

    ```php $yaml = <<<YAML null: null key true: boolean true 2.0: float key YAML;

    Yaml::parse($yaml); ```

    After:

    ```php

    $yaml = <<<YAML "null": null key "true": boolean true "2.0": float key YAML;

    Yaml::parse($yaml); ```

  • Omitted mapping values will be parsed as null.
  • Omitting the key of a mapping is deprecated and will throw a ParseException in Symfony 4.0.
  • Added support for dumping empty PHP arrays as YAML sequences:

    ```php Yaml::dump([], 0, 0, Yaml::DUMP_EMPTY_ARRAY_AS_SEQUENCE); ```

3.2.0

  • Mappings with a colon (:) that is not followed by a whitespace are deprecated when the mapping key is not quoted and will lead to a ParseException in Symfony 4.0 (e.g. foo:bar must be foo: bar).
  • Added support for parsing PHP constants:

    ```php Yaml::parse('!php/const:PHP_INT_MAX', Yaml::PARSE_CONSTANT); ```

  • Support for silently ignoring duplicate mapping keys in YAML has been deprecated and will lead to a ParseException in Symfony 4.0.

3.1.0

  • Added support to dump stdClass and ArrayAccess objects as YAML mappings through the Yaml::DUMP_OBJECT_AS_MAP flag.
  • Strings that are not UTF-8 encoded will be dumped as base64 encoded binary data.
  • Added support for dumping multi line strings as literal blocks.
  • Added support for parsing base64 encoded binary data when they are tagged with the !!binary tag.
  • Added support for parsing timestamps as \DateTime objects:

    ```php Yaml::parse('2001-12-15 21:59:43.10 -5', Yaml::PARSE_DATETIME); ```

  • \DateTime and \DateTimeImmutable objects are dumped as YAML timestamps.
  • Deprecated usage of % at the beginning of an unquoted string.
  • Added support for customizing the YAML parser behavior through an optional bit field:

    ```php Yaml::parse('{ "foo": "bar", "fiz": "cat" }', Yaml::PARSE_EXCEPTION_ON_INVALID_TYPE | Yaml::PARSE_OBJECT | Yaml::PARSE_OBJECT_FOR_MAP); ```

  • Added support for customizing the dumped YAML string through an optional bit field:

    ```php Yaml::dump(array('foo' => new A(), 'bar' => 1), 0, 0, Yaml::DUMP_EXCEPTION_ON_INVALID_TYPE | Yaml::DUMP_OBJECT); ```

3.0.0

  • Yaml::parse() now throws an exception when a blackslash is not escaped in double-quoted strings

2.8.0

  • Deprecated usage of a colon in an unquoted mapping value
  • Deprecated usage of @, `, | and > at the beginning of an unquoted string
  • When surrounding strings with double-quotes, you must now escape \ characters. Not escaping those characters (when surrounded by double-quotes) is deprecated.

    Before:

    ```yml class: "Foo\Var" ```

    After:

    ```yml class: "Foo\\Var" ```

2.1.0

  • Yaml::parse() does not evaluate loaded files as PHP files by default anymore (call Yaml::enablePhpParsing() to get back the old behavior)