element-hq / element-hq/element-ios
Kill easy warnings
Open
A-Developer-Experience
- Dominant language
- Swift
- Stars
- 1.8k
- Forks
- 544
- PR merge metrics
- PR metrics pending
Description
For stability reasons, we should remove all warnings and even consider them as errors.
Warnings due to obsoleted APIs that require too much work should be managed aside.
- [ ] MatrixSDK
- [ ] MatrixKit
- [ ] Element
- [ ] Consider warnings as errors
Contributor guide
Research direction
The issue covers warnings in MatrixSDK, MatrixKit, and Element, plus treating warnings as errors. Start by auditing the warnings and build configuration across those components. Done means warnings are removed or explicitly excluded when caused by obsolete APIs that require too much work, and the agreed warning policy is applied.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- build-system, mobile
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100