Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Refactor ScoreBox to accept ScoreBoxViewState

Open
#84 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by tracing ScoreBox, ScoreBoxViewState, GameData, mapToPeriodScores, and toPeriodScores through the view model and component. Decide whether the full view-state refactor or the smaller GameData change is intended, then verify that ScoreBox receives the chosen state and period scores still render correctly.

Written by the indexing model from the issue text.

Description

Ideally mapToPeriodScores should be done in the VM, and the ScoreBox component as a whole should accept ScoreBoxViewState instead of GameData. But if you don't want to refactor all of this right now we don't have to. For now, you could just make toPeriodScores a function on the GameData data class.

Originally posted by @zachseidner1 in https://github.com/cuappdev/score-android/pull/83#discussion_r2370251309

Dominant language
Kotlin
Stars
3
Forks
0
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cuappdev/score-android

All issues in cuappdev/score-android

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.