Idiomatic way of specifying string enum schema (use only schemas.json, needs_extra_options, or both?)

[MrChocolateMoose]

Hey guys,
In the new schemas feature, there are two ways offered to do enum schema validation (from docs):

• Using needs.extra_options

[[needs.extra_options]]
name = "asil"
description = "Automotive Safety Integrity Level"
schema.type = "string"
schema.enum = ["QM", "A", "B", "C", "D"]

• Using schemas.json

...
    "safe-need": {
      "properties": {
        "asil": { "enum": ["A", "B", "C", "D"] }
      },
      "required": ["asil"]
    },
...

In my own worked example, if I include both of these then I would get two schema violation errors (i.e. [sn_schema.extra_option_fail] for the toml based input method and [sn_schema.local_fail] for the json based input).

Since my primary means of writing schema violations would be in the schema json, I assume I should omit adding it to extra_options? Beyond rudimentary schema validation w/o wanting a dedicated schemas.json, it wasn't clear the benefit of adding it to extra_options.

Thanks!