Remove old non-ecosystem code
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by locating the ecosystem flag references mentioned in the issue and reading the surrounding code to determine which paths are non-ecosystem and obsolete. Done means the identified old non-ecosystem code has been removed without removing active ecosystem behavior.
Written by the indexing model from the issue text.
Description
Look at the ecosystem flag locations
- Dominant language
- Kotlin
- Stars
- 5
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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.
More from cuappdev/ithaca-transit-compose
-
Rpcc never open Open
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
performance
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in cuappdev/ithaca-transit-compose
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Richie97/track-history#325 ·
-
bug CLI documentation reliability
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
KW-related Type:bug UI / UX
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
RevenueCat/purchases-android#4299 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
AAswordman/Operit#1265 · 3 comments ·