arkavo-org / arkavo-org/app

🟡 MEDIUM: Address 30+ TODO/FIXME comments

Open
#217 0 comments 0 reactions 0 assignees View on GitHub
tech debt
Dominant language
Swift
Stars
0
Forks
0
Avg merge
1h 41m
Merged PRs (30d)
1

Description

## Problem

The codebase contains **30+ TODO/FIXME comments** indicating incomplete implementation or known issues.

## Notable Examples

| File | Line | Comment |
|------|------|---------|
| `AuthenticationManager.swift` | 187 | `// FIXME: major issue - user is lost from the backend` |
| `ArkavoMessageRouter.swift` | 78 | `// FIXME: hack, not sure why I am getting 064c31` |
| `ChatView.swift` | 348 | `// TODO: Notify user of failure` |

## Impact

- Technical debt accumulating
- Known bugs not being tracked
- Incomplete features shipped
- Difficult to assess project health

## Solution

1. Audit all TODO/FIXME comments
2. Create GitHub issues for each significant one
3. Either fix immediately or add to backlog
4. Remove or update comments after addressing

## Acceptance Criteria

- [ ] All TODO/FIXME comments audited
- [ ] Critical ones converted to issues
- [ ] Non-critical ones documented in backlog
- [ ] No orphaned TODO comments

Contributor guide

No contributing guide indexed for this repository

Research direction

Search the codebase for TODO and FIXME comments, then review the examples in AuthenticationManager.swift, ArkavoMessageRouter.swift, and ChatView.swift. Audit each comment, create issues for significant items, document non-critical items in the backlog, and remove or update orphaned comments.

Written by the indexing model from the issue text.

Assessment

Tech stack
swift
Domain
mobile
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.