Alexander
f807a43d58
Mirrors the weight chart pipeline (SMA + ±1σ confidence band) for body-fat %, but emits deltas from the first displayed measurement so the y-axis shows change instead of raw numbers. Title surfaces the baseline (e.g. "Body Fat · Δ from 18.2%"), y-unit is "pp" (percentage points), colours are purple trend on top of an orange raw-data line so it reads differently from weight's green+blue at a glance. FitnessChart gained two shared upgrades: `interaction.mode = 'index'` on line charts so hovering the x-axis shows tooltips for every dataset (including the trend line whose pointRadius is 0), and a `σ` dataset filter so the confidence band doesn't clutter the tooltip. A new optional `tooltipFormatter` prop lets callers format the hover label; the BF chart uses it to show the signed delta + reconstructed absolute % for raw points and additionally the ±1σ window for trend points (e.g. "+0.30 ±0.45 pp · 18.5% (18.0–18.9%)").
22 lines
2.2 KiB
Markdown
22 lines
2.2 KiB
Markdown
# TODO
|
|
|
|
## Features
|
|
[x] on /fitness/measure, fill "Past measurements" in SSR only for the last 10 measurements. anything further should be fetched client side on mount to decreae initial page load time. use a "show more" button and paginate measurments.
|
|
[x] on /fitness/measure (resp. their associated logging API routes), consolidate measurements by day. If we want to log another measurement, overwriting an old one, show a warning to indicate this. disparate measurements (e.g., weight and bodyfat) should not show this warning but simply be merged into one log entry for that day.
|
|
[x] on /fitness/measure in the past measurments tab, show more than "Body measurements only" if we don't have Bodyweight logged. we can be a bit more elaborate in our syntax here tbh.
|
|
[x] add a button on /fitness/measure/body-parts for each measurement directly below to say "Same value", instead of having to hit +, then - to lock in same number
|
|
[x] BF graph (with trend line like weight graph) on /fitness/stats page. Emphasize relative changes, not absolute numbers in design (as we cannot trust those) (e.g., use start day of overview as 0% and then show +/- x % on the graph)
|
|
[ ] Workshop better names than "Measure" for the /fitness/measure route. It's about body data points (i.e., non-food related). What's a better, short name than "Measure" to capture the logging of weight, body composition, body part measurements, and period tracking?
|
|
[ ] on /fitness/stats/histoy/<part> for body measurement graphs, make the range reasonable. e.g., if we have 1 cm change, do not fill the entire y-height with 1 cm. Use reasonable padding for low ranges (i think we do something like htis already on the weight graph?)
|
|
|
|
## Refactor Recipe Search Component
|
|
|
|
Refactor `src/lib/components/Search.svelte` to use the new `SearchInput.svelte` component for the visual input part. This will:
|
|
- Reduce code duplication between recipe search and prayer search
|
|
- Keep the visual styling consistent across the site
|
|
- Separate concerns: SearchInput handles the UI, Search.svelte handles recipe-specific filtering logic
|
|
|
|
Files involved:
|
|
- `src/lib/components/Search.svelte` - refactor to use SearchInput
|
|
- `src/lib/components/SearchInput.svelte` - the reusable input component
|