Background
From a devops Teams thread discussion (2026-07-10), the purpose of BAIUncontrolledInput was unclear even to team members. The component was created to avoid overriding localStorage on every keystroke: it intentionally removes value/onChange so that the action fires only on Enter or blur. The enter key icon exists to explicitly signal this commit-on-enter behavior.
This intent is not documented anywhere, so the Storybook documentation page (Input/BAIUncontrolledInput) should explain it.
Task
- Add a component description to the
BAIUncontrolledInput Storybook docs explaining:
- Why it is uncontrolled (no
value/onChange) — prevents expensive side effects (e.g. localStorage writes) on every keystroke
- The commit model: the new value is applied only on Enter or blur
- The meaning of the enter key icon (explicit visual cue for the commit behavior)
- Include usage guidance on when to choose it over a controlled
Input
References
- Teams thread where this was discussed (see web link)
JIRA Issue: FR-3312
Background
From a devops Teams thread discussion (2026-07-10), the purpose of
BAIUncontrolledInputwas unclear even to team members. The component was created to avoid overriding localStorage on every keystroke: it intentionally removesvalue/onChangeso that the action fires only on Enter or blur. The enter key icon exists to explicitly signal this commit-on-enter behavior.This intent is not documented anywhere, so the Storybook documentation page (Input/BAIUncontrolledInput) should explain it.
Task
BAIUncontrolledInputStorybook docs explaining:value/onChange) — prevents expensive side effects (e.g. localStorage writes) on every keystrokeInputReferences
JIRA Issue: FR-3312