Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
cmcginley-splunk opened this issue Jan 16, 2025 · 0 comments

Comments

@cmcginley-splunk
Copy link
Collaborator

  • 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
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

No branches or pull requests

1 participant