I think there is a bug with nested keys in some case. For starters I updated the merge key test to show the behavior I expect and the error that is instead produce

Items now get referenced sub-properties merged:

refDef: &reference
    subitem:
        refUnique: true
        shared: "Reference value"

item:
    <<: *reference
    subitem:
        itemUnique: true
        shared: "Item value"

OLD RESULT:

item:
    subitem:
        itemUnique: true
        shared: "Item value"

NEW RESULT

item:
    subitem:
        itemUnique: true
        shared: "Item value"
        refUnique: true

Inheritance is reversed when reference is pulled-in after all the elements:

item:
    subitem:
        itemUnique: true
        shared: "Item value"
    <<: *reference

NEW RESULT

item:
    subitem:
        itemUnique: true
        shared: "Reference value"
        refUnique: true

Inline definitions will pick-up the same behavior.

I made this little change because I am converting a LOT of data into Yaml from a database, and I wanted to make sure that the data as as user-friendly as possible.

I asked this on SO: http://stackoverflow.com/questions/34805558/phps-yaml-deciding-how-to-generate-multiline-strings

Then I discovered your wonderful YAML module, which makes much better YAML than PHP's (at least in terms of user readibility) AND it was reallllyyyy easy to hack to add this simple feature (this tells you something about the quality of your code).

Disclaimer: I don't even know PHP. I am a nodeJS boy. But, I think the patch works, and I think it's worthwhile having.

Note: I am not sure how it should deal with \n so that it's actually compatible with any Windows etc. If you feel this is a good addition, let me know and I will try and make it more generic...

Only supported in folded-scalar (lines ending with | or >) form, or inline form.

Example Yaml: items

name_enc: !!binary "SGVsbG8sIHdvcmxkLg=="
desc_enc: !!binary |
    SGVsbG8sIH
    dvcmxkLg==

According to the YAML 1.2 specs section 2.2 Structures, the Examples 2.7 and 2.8 show that the document start --- and end ... can have content (such as whitespaces and comments) before and after respectively.

The current implementation of cleanup() does not clean up the document start marker --- if the marker is placed after comments. As a result, the Parser will throw an exception.

However, in this hotfix, I've changed the regular expression in the cleanup() process such that as long as that line contains --- or ... only, we remove it.

If the markers are not used, then the usage is not affected.

Currently if you parse multiple files with the same Parser instance, you get different results in the error reporting since the parser doesn't reset the offset.

How to reproduce

<?php
include "vendor/autoload.php";

use Symfony\Component\Yaml\Parser;


$yamlString = "# translations/messages.en.yaml

sylius:
    form:
        catalog_promotion:
            action:
                fixed_price: 'Fixed price'
";

$yaml = new Parser();
$yaml->parse($yamlString);
$yaml->parse($yamlString);
try {
$yaml->parse("abc:
	abc");
} catch (\Exception $e) {
	echo $e->getMessage();
	// Returns: A YAML file cannot contain tabs as indentation at line 4 (near "	abc")
	// This is incorrect because the error is on line 2.
	// Adding more calls to $yaml->parse($yamlString) will mess with the error reporting even more
}

Hello,

As I investigated this issue, I noticed this rule which seems to me implicit. Here is the most surgical changes to obtain the expected result without break the existing output.

I have adding phpunit into project and update tests to remove coming deprecations of phpunit, because this is not bundled, and I have started the tests with my local phpunit (8).

Adding this failing test to demonstrate the issue I'm seeing. I'm afraid a fix has me puzzled for the moment.

Lines starting with a hash, within deeply-nested string blocks, are stripped from the parsed output.

Lines starting with a hash within top-level string blocks are parsed correctly and end up in the output.

So

my:
    nested:
        block: |
            This is a bit
            # of text
            as an example

Will parse to

array(
    'my' => array(
        'nested' => array(
            'block' => "This is a bit\nas an example\n"
        )
    )
)

But it should be

array(
    'my' => array(
        'nested' => array(
            'block' => "This is a bit\n# of text\nas an example\n"
        )
    )
)

But

stuff:|
    Something that
    # works well

Parses to

array('stuff' => "Something that\n# works well");

...as far as I can tell.

Make sense?

Thanks.

At present parser only substitutes aliases when mapping is in a multiline. When the alias is used in the mapping stored in a single line, alias substitution doesn't work.

So I modified Parser to fix it.

keyname1: value1     subkeyname1: a value     subkeyname2:                                 <----Must leave blank here, if previous line-value is empty!! keyname2: value2

keyname1: value1     subkeyname1: a value     subkeyname2: keyname2: value2

catch ParseException "Indentation problem."

For example, if LC_ALL is set to fr_FR then float number got ',' as separator ; example : 4,75

In order to follow Yaml Specifications (http://yaml.org/type/float.html) we must replace the comma with a dot, and specify the float type.

Code to reproduce the bug :

<?php
setlocale(LC_ALL, 'fr_FR.UTF-8', 'fr_FR.UTF8', 'fr_FR.utf-8', 'fr_FR.utf8');
require_once dirname(__FILE__) . '/symfony/src/Symfony/Component/Yaml/Escaper.php';
require_once dirname(__FILE__) . '/symfony/src/Symfony/Component/Yaml/Unescaper.php';
require_once dirname(__FILE__) . '/symfony/src/Symfony/Component/Yaml/Inline.php';
require_once dirname(__FILE__) . '/symfony/src/Symfony/Component/Yaml/Dumper.php';
require_once dirname(__FILE__) . '/symfony/src/Symfony/Component/Yaml/Parser.php';

$tab = array('value' => round(54 / 72, 4));

var_dump($tab);

$dumper = new Symfony\Component\Yaml\Dumper();
$dump = $dumper->dump($tab, 1);

var_dump($dump);

$parser = new Symfony\Component\Yaml\Parser();
$parsed = $parser->parse($dump);

var_dump($parsed);

assert($parsed === $tab);