Bypass duplicated mapping key ?

[Aktanee]

When loading a YAML file with a duplicate key, I got this message error.

{
    "name":"YAMLException",
    "reason":"duplicated mapping key",
    "mark":{...},
    "message":"duplicated mapping key at line 388, column 5:\n        last_published: \"Last published\"\n        ^"
}"

Is there a way to bypass this error and take the last value input, here, to have duplicate as true ?

test:
      duplicate: false
      duplicate: true

[puzrin]

No way. Duplicated keys are not allowed both in json and yaml.

[Aktanee]

Thanks for answering that fast, what I meant, if it wasn't clear was to have one key at the end with the last valor given (as http://www.yamllint.com/ do).

[puzrin]

I can't comment that site. May be it has reasons to not follow spec. But we checked carefully, prior to add throwing error for duplicated keys.

[Aktanee]

Ok thanks, I understand

[arcanis]

@puzrin By any chance, would you be open to reevaluate this? We're using js-yaml on Yarn (our lockfiles are now regular Yaml), and to make our users' life easier we try to gracefully recover from lockfile merge conflicts (basically we parse both current and incoming versions of the lockfile, then merge them together). It turns out that in some circumstances Git will generate a bogus lockfile that duplicates some keys.

In our case it's not a big deal (it's best effort recovery, and both entries contain the same data anyway), but the lack of option to signal to js-yaml that it should just ignore the problem means that we sometimes have to throw pretty annoying errors:

➤ YN0046: The individual variants of the lockfile failed to parse

When that happens, there's no other choice for the user than remove the lockfile, and lose all their current locked resolutions. It's not a great experience 🙁

[puzrin]

@arcanis ok, create a new issue with this details please. Need to think.