mitre-attack / mitre-attack/attack-workbench-frontend
Bug: comparing a collection to itself
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 438
- Forks
- 79
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 3
Description
When viewing/editing a collection that has been marked for release, the latest (previously) released version is retrieved for comparison. If the collection being viewed/edited is the first and only version of the collection, it will be compared against itself, incorrectly listing new or changed objects as "unchanged".
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 by reproducing the comparison while viewing or editing a collection marked for release when it has only one version, then trace where the previously released version is selected. Done means the first version is not compared with itself and its new or changed objects are no longer reported as unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100