-
Notifications
You must be signed in to change notification settings - Fork 209
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.
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
Complex YAML generates many linting errors #712
Complex YAML generates many linting errors #712
Comments
I think our parse recognizes keys such as |
Reasonable point of view. Yaml prettifiers will change [5,5] to ‘5,5’==a string. I can really use either.
Julialang’s yaml package does convert the [5,5] to a vector and can (bizarrely compared to Python for example) use it as a Dict key because it’s hashable.
From: Gorkem Ercan ***@***.***>
Reply-To: redhat-developer/vscode-yaml ***@***.***>
Date: Saturday, March 12, 2022 at 1:44 PM
To: redhat-developer/vscode-yaml ***@***.***>
Cc: Lewis Levin ***@***.***>, Author ***@***.***>
Subject: Re: [redhat-developer/vscode-yaml] Complex YAML generates many linting errors (Issue #712)
I think our parse recognizes keys such as[5,5] as flow sequences. I am not sure if that is proper usage, I need to read the specification a bit more. @eemeli<https://github.com/eemeli> any ideas on that one.
—
Reply to this email directly, view it on GitHub<#712 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAIYWLO4M5ZPJ7UIIESSXFDU7UF4RANCNFSM5QODXBWQ>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
This was a bug in |
Thanks, @eemeli for looking at this quickly |
Second that!
From: Gorkem Ercan ***@***.***>
Reply-To: redhat-developer/vscode-yaml ***@***.***>
Date: Sunday, March 13, 2022 at 12:56 PM
To: redhat-developer/vscode-yaml ***@***.***>
Cc: Lewis Levin ***@***.***>, Author ***@***.***>
Subject: Re: [redhat-developer/vscode-yaml] Complex YAML generates many linting errors (Issue #712)
Thanks, @eemeli<https://github.com/eemeli> for looking at this quickly
—
Reply to this email directly, view it on GitHub<#712 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAIYWLLOKUD67JIYKLDKSKTU7ZJA5ANCNFSM5QODXBWQ>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Describe the bug
You'll see the example below, but I get these linting errors:
I do use the same keys in DIFFERENT mappings. There are no duplicate map keys within a mapping.
Finally, onlineyamltools.com validate yaml tool is very happy with it. Note also that githubs markdown processor seems ok because it syntax highlights the yaml text with no problems.
For non schema related issues please post the relevant YAML along with any other info that
may be relevant.
-->
Expected Behavior
There shouldn't be any linting errors based on my use of other yaml validation tools.
Current Behavior
repeated errors show up in the linter
Environment
The text was updated successfully, but these errors were encountered: