Switch 'src validate' to use yaml.v3 #431
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes #429 by switching
src validateto useyaml.v3.When trying to confirm that it still works, I found out that parsing the validate input as YAML didn't work for me, even without the change.
Both
yaml.v3andyaml.v2assume that the fields in the YAML are insnake_caseand need tags added to the struct fields to make it work withcamelCase.The
github.com/ghodss/yamlworks withsnake_caseand also supports the unmarshalling into a*json.RawMessage, whichyaml.v2andyaml.v3don't support.But since the goal was to only use a single YAML library I switched to
yaml.v3and changed the code to work with it. I tested this locally and checked that everything's unmarshalled correctly.'See the script here for how I explored this (and learned to curse YAML yet again).
That prints: