Skip to content

Conversation

brondani
Copy link

@brondani brondani commented Sep 1, 2023

According to YAML spec 1.2.2:

The content of a mapping node is an unordered set of key/value node pairs, with the restriction that each of the keys is unique.

The changes proposed here check the uniqueness of scalar mapping keys, throwing a NonUniqueMapKey exception when by inserting a new key/value pair an identical scalar key is already present in a mapping. Non identical but equivalent scalar content, for example “0o13” (octal) or “0xB” (hexadecimal), are not considered.

Address #60.

@apirogov
Copy link

Would like to see this merged. It's a common source of problems to have duplicate keys in a map and have the content being overridden silently. We have huge config files with YAML and it's easy to miss an existing entry and duplicate it, causing issues due to the silent overriding.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants