Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Improve JSON compatibility #189

Merged
merged 12 commits into from Sep 6, 2020
Merged

Improve JSON compatibility #189

merged 12 commits into from Sep 6, 2020

Commits on Aug 23, 2020

  1. Add replacer argument for stringify, new Document & doc.createNode 

    As replacer & options have different shapes, YAML.stringify and the
Document constructor can still accept the options as the second
argument.

The behaviour of the replacer should match the JSON.stringify equivalent
exactly for the values both support. Map is treated equivalently to an
Object; others act like arrays.
    @eemeli
    eemeli committed Aug 23, 2020
    Copy the full SHA
    f028c13 View commit details
    Browse the repository at this point in the history

Commits on Aug 30, 2020

  1. Use correct this in replacer calls

    @eemeli
    eemeli committed Aug 30, 2020
    Copy the full SHA
    c3d860e View commit details
    Browse the repository at this point in the history

  2. Rename toJSON() as toJS() internally 

    BREAKING CHANGE: The `toJSON()` utility exported by 'yaml/util' is
renamed as `toJS()`.
    @eemeli
    eemeli committed Aug 30, 2020
    Copy the full SHA
    6d28ef2 View commit details
    Browse the repository at this point in the history

  3. Add Document#toJS(), drop keepBlobsInJSON option

    @eemeli
    eemeli committed Aug 30, 2020
    Copy the full SHA
    329af83 View commit details
    Browse the repository at this point in the history

  4. Add JSON reviver support to YAML.parse() and doc.toJS()

    @eemeli
    eemeli committed Aug 30, 2020
    Copy the full SHA
    e6a9ff7 View commit details
    Browse the repository at this point in the history

  5. Update docs for resolver & reviver

    @eemeli
    eemeli committed Aug 30, 2020
    Copy the full SHA
    8f5de1d View commit details
    Browse the repository at this point in the history

  6. Encode strings with unpaired surrogate code points as double-quoted 

    This effectively implements this ECMA-262 proposal:
https://github.com/tc39/proposal-well-formed-stringify
    @eemeli
    eemeli committed Aug 30, 2020
    Copy the full SHA
    4242c08 View commit details
    Browse the repository at this point in the history

  7. Allow third arg of YAML.stringify to be a number or string setting in… 

    …dent
    @eemeli
    eemeli committed Aug 30, 2020
    Copy the full SHA
    d4b759e View commit details
    Browse the repository at this point in the history

  8. Fix replacer call on Set to use value as key, rather than index

    @eemeli
    eemeli committed Aug 30, 2020
    Copy the full SHA
    10bf80a View commit details
    Browse the repository at this point in the history

  9. Skip unpaired surrogate pair tests on Node.js < 12

    @eemeli
    eemeli committed Aug 30, 2020
    Copy the full SHA
    43fd284 View commit details
    Browse the repository at this point in the history

  10. Update playground

    @eemeli
    eemeli committed Aug 30, 2020
    Copy the full SHA
    ef1e4f5 View commit details
    Browse the repository at this point in the history

Commits on Sep 6, 2020

  1. Merge branch 'master' into json-like

    @eemeli
    eemeli committed Sep 6, 2020
    Copy the full SHA
    c5fb6ca View commit details
    Browse the repository at this point in the history