mitre-attack / mitre-attack/attack-workbench-frontend
Restrict deletion to objects which have not been exported or published
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 438
- Forks
- 79
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 3
Description
Add the ability to determine if the object has previously been exported or published. If the object has been previously published or exported, users should not be able to delete the object from the database.
For references, they cannot be deleted if they are used by any objects OR have been on an object at the time it was exported or published at any point.
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
No files, tests, or entry points are named in the issue. Start by locating object deletion and export or publish flows, then determine how the requested historical state should be represented; done means previously exported or published objects and affected references cannot be deleted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- database, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100