Update Spyc to 0.6.2: Fixes parsing error array entry on multiple lines

[blynx]

Hi,

I had a parsing issue where FieldtypeYaml threw the "Current level has both int and str keys, ..." exception. Spyc didn't correctly parse an array like this:

array:
    - "lorem"
    - "ipsum"
    - "dolor
    this is the other line which is mistaken for a new key but belongs to 'dolor'"

I replaced Spyc with the newest version and it solved that problem.
https://github.com/mustangostang/spyc/

Cheers,
Steffen

[owzim]

Hi @blynx, thanks for the hint. I updated the dev branch. Will not merge into master just yet since there have been a couple of updates.

[blynx]

Nice!

Will the other updates actually handle the "Current level has both int and str keys" thing?
Ran into this a couple of times and I don't really get why this is needed. Probably something temporary?

Built my own module/wrapper for the PECL yaml extension now. Maybe you could consider making this optional? Or use Spyc as a fallback.

[owzim]

Where is this wrapper? I could build in, that it uses that module, if it exists (is installed).

[owzim]

Current level has both int and str keys, thus it's impossible to keep arr or convert to obj It's not possible with anything but parseAs='Associative Array'. How should an object/WireArray be constructed if it has both? object cannot have int keys, WireArray can, but str keys would only be properties of that WireArray and not be iterable, AND its child elements must be objects. What kind of scenario do you have where you would want both int and str keys?

[blynx]

Uhhmm, yep, I thought WireData/Array support them anyway so it doesn't really matter - but I don't remember now what setting I actually used! Thats true for objects ...

Oh, it's almost nothing, basically just replace the yaml parsing function somehow:

if (!extension_loaded('yaml')) {
    ...
} else {
    yaml_parse( $yaml_data );
}

This is the extension: https://pecl.php.net/package/yaml

[owzim]

@blynx Updated the dev branch to include your code.