Skip to content

Enforce that field names are not repeated across risk objects as part of build/validate #347

@cmcginley-splunk

Description

@cmcginley-splunk
  • For risk and threat objects, we expect each field to be used for a single entry, not multiple
  • We check against this at runtime during testing, but it could be enforced by validators as well

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions