MozillaSecurity / MozillaSecurity/FuzzManager
[FTB][CrashManager] auxCrashData and crashdata names are inconsistent
Open
Nobody has claimed this yet.
enhancement
FTB
help wanted
- Dominant language
- Python
- Stars
- 208
- Forks
- 48
- Avg merge
- 23h 5m
- Merged PRs (30d)
- 2
Description
We should decide what to call crashdata and use that consistently throughout the API and UI. "aux" also implies that it is less important when it is actually the most preferred field.
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 every use of auxCrashData and crashdata in the API and UI. Decide on one canonical name, document that choice, and update all references so the API and UI use it consistently. Done means neither competing name remains in the affected interfaces.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend, frontend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100