prettier / yaml-unist-parser Goto Github PK

View Code? Open in Web Editor NEW

23.0 6.0 9.0 858 KB

A YAML parser that produces output compatible with unist

License: MIT License

JavaScript 0.85% TypeScript 99.15%

unist yaml

yaml-unist-parser's People

Contributors

Stargazers

Watchers

Forkers

saudi-arabia-riyadh wtcross fisker sosukesuzuki thorn0 qpc-github quantum-platinum-cloud jounqin

yaml-unist-parser's Issues

Can you update `yaml`

the dependency yaml has been changed a lot, can you please update it?

Update typescript & jest

I was not able to fix issues in #281

@sosukesuzuki Can you work on it?

Comments in `flowMapping` and `flowSequence` not correctly attched

a: 
  [
    foo,
    # comment
  ]

And

b: 
  {
    bar: baz,
    # comment 2
  }

Prettier issue prettier/prettier#8377

EndComment mis-attaching in nested mapping

Version

[email protected]
[email protected]

Input

parent:
  one: 1
  # two: 2

Output

The comment is attached to children in documentBody.

Expected

The comment is attached to endComments in parent's mappingValue.

Original post: prettier/prettier#4917

Use `new YAML.Document().parse(ast)` to find syntax errors

Context: prettier/prettier#4563 (comment)

Waiting for the patch release for

Update `yaml`

When updating yaml to v1.10.0 can't parse following code

empty block scalar: >
 
  
   
 # comment

See prettier/prettier#8349

Update `yaml` to v2

[email protected] has been released for a while, it will be great if we can support that.

https://github.com/eemeli/yaml/releases

Comment inside map crashes with CRLF line endings

map:
# with CRLF this comment causes: Unexpected leading character "\n"

It works fine with LF line endings.

Also this library is great! 🎉

Please update `tslib` version requirement

https://unpkg.com/browse/[email protected]/lib/transforms/document-head.js

Line 11 use __spreadArrays, this requires [email protected], but the version requirement in package.json is ^1.9.1 https://github.com/ikatyang/yaml-unist-parser/blob/2617e8aaede2272d912dffe7f21a2b3b654ea9fe/package.json#L30 causes error

Migrate to typescript-eslint from tslint

https://palantir.github.io/tslint/

⚠️ TSLint has been deprecated as of 2019. Please see this issue for more details: Roadmap: TSLint → ESLint. typescript-eslint is now your best option for linting TypeScript.

tslint has been deprecated, so we need to migrate typescript-eslint.

Comments at the end of a collection

Ref: prettier/prettier#4843

Incorrect documentHead position

# --

          "position": {
            "start": { "offset": 0, "line": 1, "column": 1 },
            "end": { "offset": 0, "line": 1, "column": 1 }
          },

# ---

          "position": {
            "start": { "offset": 2, "line": 1, "column": 3 },
            "end": { "offset": 5, "line": 1, "column": 6 }
          },

Prettier issue prettier/prettier#8378

Support YAML Inline Extend syntax

foo:
 <<: &anchor
   K1: "One"
 K2: "Two"

bar:
 <<: *anchor
 K3: "Three"

Ref: prettier/prettier#8876

Comment attach seems wired

In this, comment 1 is attached as endComments,

- a
  # comment 1
- b
  # comment 2

When next one is longer, comment 1 is attached as leadingComments,

- a
  # comment 1
- bb
  # comment 2

Same problem in map

a:
  # comment 1
b:
  # comment 2

a:
  # comment 1
bb:
  # comment 2

Context: prettier/prettier#9143 (comment)

yaml-unist-stringify?

Any plans to implement stringify? This would make it a full unified processor 😇

Drop Node.js <= 12.x ?

Prettier v3 supports Node.js >= 14.x so I think that yaml-unist-parser also should drop Node.js <= 12.x.

(It will be breaking change, so we need major release)

Type compatibility with `unist-util-visit`

Hi, while the parser is compatible with unist, the types do not seem to be compatible. Using the visit function from unist-util-visit, I get the following type error:

Argument of type 'Root' is not assignable to parameter of type 'Node'.
  Index signature is missing in type 'Root'.

Comment after anchor attach

key: &anchor
  # comment
  - value

comment is attached as sequence.middleComments, maybe better sequenceItem.leadingComments?