Repository navigation
[Mobile] Reports: burndown, velocity, CFD, created vs resolved - #33
Merged
Merged
Conversation
Closes #13. Charts are drawn with react-native-svg, which is already here for the icon set, rather than adding a charting library: four fixed shapes need a fraction of what one provides, and tapping for a value is easier to get right when the hit areas are ours. Every number comes from the same event-history endpoints the web charts and none is recomputed here, which is what makes the figures match rather than merely agree. The burndown's ideal line included -- the client draws, it does not model. A fingertip covers several days at phone width, so a tap reads the nearest point rather than demanding an exact hit, and the readout row is reserved rather than conditional so the layout does not jump as a finger moves. The "history before tracking began cannot be reconstructed" notice is carried over from web, and every chart has an empty state, because a fresh instance has no history at all -- there is a test that the scales survive that rather than dividing by zero. Co-Authored-By: Claude Opus 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
1 participant
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.
Closes #13.
Charts are drawn with
react-native-svg, already present for the icon set, rather than adding a charting library: four fixed shapes need a fraction of what one provides, and tapping for a value is easier to get right when the hit areas are ours.Every number comes from the same event-history endpoints the web charts and none is recomputed here, which is what makes the figures match rather than merely agree — the burndown's ideal line included.
A fingertip covers several days at phone width, so a tap reads the nearest point rather than demanding an exact hit, and the readout row is reserved rather than conditional so the layout does not jump.
The "history before tracking began cannot be reconstructed" notice carries over from web, and every chart has an empty state — a fresh instance has no history at all, and there is a test that the scales survive that rather than dividing by zero.