mitre-attack / mitre-attack/attack-workbench-frontend
Move Tactic Validation for Techniques from ATT&CK Workbench Frontend to the Backend
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 438
- Forks
- 79
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 3
Description
ATT&CK Worbench frontend should move validation and existence of a tactic for a technique to the backend and let the ATT&CK Data Model handle validation. Below validation should be remove from src/app/classes/stix/technique.ts
// only check tactics if object is not a draft
result.errors.push({
field: 'tactics',
result: 'error',
message: 'object has no tactics',
});
}
Related ATT&CK Data Model issue
Contributor guide
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 in src/app/classes/stix/technique.ts and review the validation block shown in the issue, then read the related ATT&CK Data Model issue for the backend ownership context. Remove the frontend tactic-existence validation, with completion shown by the data model/backend handling that validation instead.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 82/100