Marc-André Bombeck 8e6880b04c Say when the onboarding profile step could not save a field ...

The baseline step submitted what you filled in and ignored the answer.
The profile write is field-independent: it stores everything that
validated and reports back what it declined. Nobody read that report
here, so a value the server refused vanished between the input and the
next screen and you moved on believing it was saved.

It now says which field did not make it, using the name that sits next
to the input you typed into, and keeps going with the rest that did
save. When nothing could be saved at all, the step stays put and names
the field that blocked it instead of a shrug. The wording and the
field-naming come from the same place the account form in Settings
uses, so the same refusal reads the same wherever you hit it.

2026-07-31 07:58:45 +02:00

..

__tests__

fix(insights): scope generation guard to prompt fields, clear cache on restore

2026-07-28 21:11:43 +02:00

health-facts.ts

fix(insights): scope generation guard to prompt fields, clear cache on restore

2026-07-28 21:11:43 +02:00

height-unit-display.ts

feat(profile): enter and show height in the selected unit

2026-07-25 08:21:42 +02:00

rejected-fields.ts

Say when the onboarding profile step could not save a field

2026-07-31 07:58:45 +02:00

sex.ts

refactor(profile): route every binary-sex narrow through the one owner

2026-07-27 14:47:54 +02:00