element-hq / element-hq/element-ios
Build: Kill warnings
Open
code-quality
maintenance
- Dominant language
- Swift
- Stars
- 1.8k
- Forks
- 544
- PR merge metrics
- PR metrics pending
Description
In the past, Riot build had 0 warnings. Now, there are 1000+.
Moreover, Xcode made the life stupidly hard to find errors among warnings.
Anyway, we should kill them.
Contributor guide
Research direction
Start by running the Riot build in Xcode and inventorying the reported warnings. The issue names no files or tests; done means the build's warning count is reduced to the expected level, with errors easier to identify.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- build-system, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100