yaml icon indicating copy to clipboard operation
yaml copied to clipboard

YAML parser and stringifier for JavaScript

Results 28 yaml issues
Sort by recently updated
recently updated
newest added

**Describe the bug** I am creating custom tags that handles non scalar values. The way the yaml is formatted though is unexpected. See below: Expected: ``` foo: bar: !append -...

enhancement

This enables the resolution of YAML looking like this: ```yaml - &foo bar: - 1 - 2 - 42 - *foo/bar/2 ``` to resolve as: ```js [ { bar: [1,...

next

**Is your feature request related to a problem? Please describe.** I have a situation where I have a list of paths from a YAML document. I need to map these...

enhancement

**Describe the bug** CST.setScalarValue() does not preserve non-semantic indentation for block scalars **To Reproduce** Apply setScalarValue() to change the content of a 4-space indented block scalar value in an unindented...

bug

The round trip for editing documents while preserving comments is understandably complex. It seems plausible to wrap `YAML.Document.Parsed` in a [Proxy](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy) which can be read similarly to the results of...

enhancement

**Describe the bug** First of all, thanks for an awesome yaml parser/stringifyer! I just wrote this this weekend: [yaml-diff-patch](https://github.com/grantila/yaml-diff-patch) using this library to allow modifying a yaml using JSON patches....

enhancement
help wanted

**Describe the bug** If there's a large block of comments hanging indented under a key, that can trigger an error suggesting that the next key indicator is too far away....

bug

We yamlify markdown, which often contains long-ish URLs. We would like to have the yaml not break those URLs up, so the yaml is easier to read, and so they...

enhancement

**Describe the bug** When parsing a document like this: ```yaml foo: *bar ``` The `errors` array on the parsed document is empty, and `toJS` will throw `ReferenceError: Unresolved alias` **To...

bug

**Describe the bug** Inconsistent behaviour of parseDocument function. Once yaml contains deep hierarchical of empty nodes the comment from the next node on a top level is getting ignored. Instead...

bug