We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug The following is valid yaml:
foo: -
but the code treats this as an error:
[2:1] empty sequence entry 1 | foo: > 2 | - ^
See: https://yaml.org/spec/1.2.2/#72-empty-nodes
To Reproduce
https://go.dev/play/p/RHQfxSlvxTK
There's even a unit test that expects an error from valid yaml: https://github.com/goccy/go-yaml/blob/master/parser/parser_test.go#L686
a: - b: c -
If you feed that into https://www.yamllint.com/, https://yamlchecker.com/, gopkg.in/yaml.v2, and gopkg.in/yaml.v3, they all say that's valid yaml.
Expected behavior
An empty sequence should be treated as if it were the "zero value"
Version Variables
Additional context I believe this might be related to #313 and #168.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
The following is valid yaml:
but the code treats this as an error:
See: https://yaml.org/spec/1.2.2/#72-empty-nodes
To Reproduce
https://go.dev/play/p/RHQfxSlvxTK
There's even a unit test that expects an error from valid yaml: https://github.com/goccy/go-yaml/blob/master/parser/parser_test.go#L686
If you feed that into https://www.yamllint.com/, https://yamlchecker.com/, gopkg.in/yaml.v2, and gopkg.in/yaml.v3, they all say that's valid yaml.
Expected behavior
An empty sequence should be treated as if it were the "zero value"
Version Variables
Additional context
I believe this might be related to #313 and #168.
The text was updated successfully, but these errors were encountered: