stadiamaps / stadiamaps/ferrostar
Ensure that all internal modules that should use TripState are using it
Open
chore
core
- Dominant language
- Kotlin
- Stars
- 419
- Forks
- 81
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 7
Description
I think we've already done this for the waypoint/step advance, route deviation, etc., but take a second pass through everything before 1.0 to make sure we're using it wherever needed.
Contributor guide
Research direction
Start by reviewing the internal modules involved in waypoint/step advance and route deviation, then inspect other pre-1.0 modules for consistent TripState usage. Done means every module that should use TripState does so, but the issue names no files, entry points, or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile-dev
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100