Enforce that field names are not repeated across risk objects as part of build/validate
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 139
- Forks
- 52
- Avg merge
- 1h 16m
- Merged PRs (30d)
- 3
Description
- 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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the build/validate entry points and the existing runtime testing check for repeated fields in risk and threat objects. Trace how validators report invalid objects, then make duplicate field names fail validation and confirm the behavior through the relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100