Repository navigation
fix(trends): call the range-average card what it is, below the range it averages - #2901
Open
UtkuDenizAltiok wants to merge 1 commit into
Open
UtkuDenizAltiok wants to merge 1 commit into
UtkuDenizAltiok wants to merge 1 commit into
Conversation
…it averages Trends opens with the week digest (this week's Charge / Effort / Rest), then a card titled "Week in review" whose numbers are the means over the range window selected BELOW it (3M by default). So the screen showed two different "this week" figures a few lines apart: in the demo data, the digest's Charge 50 and the card's 41, which was the 90-day mean. The card now sits directly below the range control and is titled "Average" (overline unchanged: Charge · Effort · Rest), so it reads as the average of the range the wearer just chose. The digest at the top keeps the "Week in review" name it actually describes. Values, the window resolution and the card itself are unchanged. Both platforms, same order and title. Reuses strings that already ship in every locale (Apple "Average", Android explore_average), so no translation changes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
UtkuDenizAltiok
added a commit
to UtkuDenizAltiok/noop
that referenced
this pull request
Nov 5, 2026
Tree is exactly 4a6a22c: upstream/main + every open app PR + Simple mode (Today, More, Sleep, Trends) + ryanbr#2897 ryanbr#2898 ryanbr#2899 ryanbr#2900 ryanbr#2901 (the ryanbr#2896 swipe fix is already inside Simple mode) + the parity refresh. Recorded as a merge over the previous stack so the branch moves forward without rewriting history. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
UtkuDenizAltiok
added a commit
to UtkuDenizAltiok/noop
that referenced
this pull request
Nov 5, 2026
…nbr#2900 ryanbr#2901 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What was wrong
Trends opens with the week digest (this week's Charge / Effort / Rest), then a card titled "Week in review" whose numbers are the means over the range window selected below it (3M by default). So the screen showed two different "this week" figures a few lines apart. In the demo data: the digest's Charge 50, then the card's 41, which was the 90-day mean.
The fix
The card now sits directly below the range control and is titled "Average" (overline unchanged: Charge · Effort · Rest), so it reads as the average of the range the wearer just chose. The digest at the top keeps the "Week in review" name it actually describes. Values, window resolution and the card itself are unchanged.
Both platforms, same order and title. Reuses strings that already ship in every locale (Apple
"Average", Androidexplore_average), so no translation changes.Verification
i18n_audit.py --ci upstream/mainpasses;doc_comment_lint.pyclean.rangeBarand the header literal changes; Android change: theWeekInReviewCarditem moves below the range control item and its header usesexplore_average. CI's App build and Android jobs compile both.🤖 Generated with Claude Code