forked from ghodss/yaml
-
Notifications
You must be signed in to change notification settings - Fork 86
Strict unmarshalling should be case-sensitive #15
Copy link
Copy link
Open
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Metadata
Metadata
Assignees
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Using
yaml.UnmarshalStrict(...)compares keys in a case insensitive way.I would expect it to do case sensitive comparisons of key names so that if I define a key in my schema called
somethingGreat, a key in a yaml file calledsomethingGREatwouldn't match, and the unmarshal would fail with the errorunknown field "somethingGREat".