Re: Option to enforce unique map keys
Zenaan Harkness <[email protected]>
| Newsgroups | gmane.text.yaml.general |
|---|---|
| Message-ID | <CAOsGNST1gCywqM50tLGeLAXEYUHM8B1Q6_4fznbKk0=suob-Ww@mail.gmail.com> |
On 9/24/14, Mark Laff <[email protected]> wrote: > While the YAML spec specifies that Mapping node keys must be unique [1.2 > spec, section 3.2.1.1 Nodes], it seems like duplicate keys are not flagged. Parsers "should" match the spec by default and optionally provide options to bend to something outside the spec, IMEHO. > For example: ... > I suggest adding an option to the Yaml parser to I don't know which library you are referring to. Does it have a bug-report page or email address? Good luck, Zenaan -- Banned for life from Debian, for suggesting Debian's CoC is being swung in our faces a little too vigorously. ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk