yaml VS gojsonschema

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

Also bear in mind your own ability to take the project, fork it, and merge in a PR or two you may really need. I understand taking on full maintenance is probably too much on a project with 100+ PRs, but don't forget that if you have a couple of things that you need with a big bang-for-the-buck that you can always do it yourself, and you have the full power of git backing you as you maintain your branch. I've got a couple forks of things where I'm just basically maintaining a single patch on top of it. Most are internal but here's a public one I can show you, where I've added something I really needed for my project, but is probably of no interest to the original maintainer or anybody else. Right now, conveniently for me, Github is even showing that I'm a commit behind the original; what you can't see is that I've already pulled in two previous updates from the original branch in the past. You need to pick cases where you get good bang-for-the-buck, but if you need it, don't be too afraid. (Be a little bit afraid; it is some extra maintenance burden, and that shouldn't be counted as zero. But it's not infinitely bad, either.)