yaml VS go-yaml

For the last six years I've primarily been coding in Golang. Primarily against k8s. It is painful that the defacto YAML library for Go (https://github.com/go-yaml/yaml) is neither a YAML 1.1 nor a YAML 1.2 encoder/decoder.

Technically that qualifies as yaml, so you could maybe use go-yaml/yaml

Is it possible to replicate this (or something on those lines) in GoLang? I've tried go-yaml 3.0.0 but i've got no luck. I've gotten something with go-gypsy 1.0.0 (as seen below) but i was not able to use it...

Unfortunately, all Go YAML parsers that I know of, including the most commonly used go-yaml (originally created by Canonical), will choke when you try to parse such YAML into interface{}, because they try to force it into a Go map, which has many limitations on keys. And you cannot unmarshal it into ny Go map, either, for the same reason.

I see if you go to the project page with no parameters, Github presents you the v2 branch. Be sure to check out the v3 branch, which I've been using. It allows better access to the parse tree during unmarshaling, and I've used it to good effect. For instance, I have a "notification" unmarshaler that allows you to do either:

This is post is about converting go struct/map into a yaml using this amazing go package go-yaml

Going to sound like a stupid question, but why aren’t you using a marshaller like https://github.com/goccy/go-yaml ?

Stop using go-yaml/yaml... use https://github.com/goccy/go-yaml instead which is much better maintained and user friendly. :)

Honestly, I would rather use https://github.com/goccy/go-yaml which is a lot classier.