Giters
go-yaml
/
yaml
YAML support for the Go language.
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
6871
Watchers:
98
Issues:
676
Forks:
1051
go-yaml/yaml Issues
Marshaling integer values to hexadecimal representation
Updated
a month ago
Comments count
1
panic while unmarshall
Updated
a month ago
Custom unmarshalling with support for known fields
Updated
a month ago
Comments count
1
Yaml encoder writing tag of merge node `!!merge` in output
Updated
2 months ago
Comments count
2
Line comment, when used with yaml tag, is unmarshalled to incorrect yaml node.
Updated
2 months ago
V3 unmarshal interface does not support unmarchal object partially.
Updated
2 months ago
Force marshaler to use multi-line for string with `\n`
Updated
2 months ago
Comments count
2
Invalid json will be unmarshal into a wrong result without throw error
Updated
2 months ago
key y is given double quotes while unmarshalling
Closed
2 months ago
Comments count
3
Does the documentation for Decoder.KnownFields make grammatical sense?
Updated
3 months ago
Default values (again!!)
Updated
3 months ago
Comments count
6
Encode does not respect Style = LiteralStyle
Updated
3 months ago
excute home page code, the output space is 4
Closed
4 months ago
Comments count
2
Unmarshal drops lines and does not return error
Closed
4 months ago
Comments count
1
Module abandoned?
Closed
4 months ago
Comments count
4
Merge doesn't work as expected
Updated
5 months ago
Increased memory consumption when serializing long slices.
Updated
5 months ago
Invalid date-time format during marshalling returns unquoted value. Expecting quoted value.
Updated
6 months ago
Comments count
2
Unmarshaler ignored: cannot parse 'ReadOnly' as int: strconv.ParseInt: parsing "deny": invalid syntax
Updated
6 months ago
Comments count
1
UnmarshalText ignored in arrays
Updated
6 months ago
Comments count
1
yaml omitempty
Updated
6 months ago
Comments count
2
`flow` and `inline` structure tags don't work together
Updated
7 months ago
Different behaviors between this library and standard encoding/json when unmarshal yaml to a struct embedded with other structs
Updated
7 months ago
Comments count
1
Why were the patch versions for CVE-2021-4235 released so late?
Updated
8 months ago
Comments count
1
Incompatible with standard `encoding/json` regular expression marshaling
Updated
8 months ago
Comments count
1
Newline string literals produce invalid marshaling output
Updated
8 months ago
Comments count
2
YAML parsing is not as expected
Closed
8 months ago
Comments count
2
Yea
Closed
8 months ago
Incorrect RC3339 encoding
Closed
8 months ago
Comments count
1
mining
Updated
8 months ago
Custom (Un-)Marshaller on Generic Types ignored
Updated
8 months ago
Untagged field names "y" and "n" marshalled with quotes, others not
Closed
9 months ago
Comments count
6
Comments rendering issue related to array nodes
Updated
9 months ago
Inconsistent behaviour when marshalling strings
Updated
9 months ago
Comments count
1
Indentation problem
Updated
9 months ago
Comments count
1
Empty `!!null` node fails encoding and causes panic
Updated
10 months ago
v3 skips blank elements in a sequence whereas v2 does not
Updated
10 months ago
Comments count
1
Feature request: Find and get information of a Node based on yaml path
Updated
a year ago
Stack overflow when calling value.Decode inside of structure
Updated
a year ago
Comments count
1
[feature] extended Marshaler interface with passing extra parameters
Updated
a year ago
[feature]: support to add comments in yaml
Updated
a year ago
Add option to use YAML v1.2 octal syntax only
Updated
a year ago
How to marshal objects to `yaml.Node`?
Closed
a year ago
Comments count
3
how to decode a yaml.Node document ?
Updated
a year ago
yml.Unmarshal It doesn't erase the previous content
Updated
a year ago
Windows line endings issue
Updated
a year ago
How to parse nested map[int]int
Closed
a year ago
Indefinite recursion in decoder.prepare()
Updated
a year ago
[BUG] omit to unset flag 'space_break' in emitterc.go
Updated
a year ago
Invalid yaml data portion parsed with no error
Updated
a year ago
Comments count
2
Previous
Next