-
-
Notifications
You must be signed in to change notification settings - Fork 156
Issues: goccy/go-yaml
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Tabs before colons in keky:values are rejected, but only sometimes
bug
Something isn't working
parser
#675
opened Mar 6, 2025 by
eugenesvk
scanner.Scanner/lexer.Tokenize does not properly decrement IndentLevel
bug
Something isn't working
#672
opened Feb 24, 2025 by
nmiyake
The indentation has been striped from the []byte passed to UnmarshalYAML.
bug
Something isn't working
#670
opened Feb 22, 2025 by
k1LoW
Feat: Allow ignoring fields with a certain prefix with strict unmarshalling
feature request
#669
opened Feb 21, 2025 by
cpuguy83
Question: How can I parse multi yaml file?
question
Further information is requested
#664
opened Feb 17, 2025 by
wrbbz
Feature/question: how to distinguish between unparsed data and strings?
question
Further information is requested
#661
opened Feb 16, 2025 by
felixfontein
Path skip commented content in the result of ReadNode.
bug
Something isn't working
#659
opened Feb 15, 2025 by
yudintsevegor
Wrong indentation when path.ReplaceWithNode with an ast.Node created by the function yaml.ValueToNode
bug
Something isn't working
#636
opened Feb 4, 2025 by
caormarc
Incorrect indentation for block sequence with newlines
bug
Something isn't working
encoder
#626
opened Jan 22, 2025 by
shuheiktgw
Passing a double pointer to decoder.Decode has unexpected result
decoder
feature request
#619
opened Jan 16, 2025 by
zfLQ2qx2
Indent
EncodeOption
ignored when encoding ast.Node
bug
#614
opened Jan 10, 2025 by
braydonk
Comments cannot be extracted from Flow-style YAML
bug
Something isn't working
#608
opened Jan 1, 2025 by
shuheiktgw
path.Replace changing type creates a weird yaml result
bug
Something isn't working
#607
opened Dec 23, 2024 by
gkampitakis
Question: Why interfaces can be marshaled but not unmarshaled by default?
question
Further information is requested
#577
opened Dec 8, 2024 by
gabyx
Tokenizer line numbers incorrect with Windows line endings
bug
Something isn't working
parser
#560
opened Nov 30, 2024 by
cedws
Perform partial unmarshaling with
yaml.DisallowUnknownField()
feature request
#491
opened Oct 30, 2024 by
ekoops
Lexer and Parser information for creating intelisense support
feature request
low priority
#468
opened Jul 24, 2024 by
torabian
Increased memory consumption when serializing long slices.
enhancement
New feature or request
low priority
#451
opened May 31, 2024 by
RekGRpth
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.