Skip to content

Refactor: unify the two form-error components #1469

Description

@Baskarayelu

Summary��uni

y the two
orm-error components.��## Background��We want to keep the cross-border remittance UI auditable and sa
e to change. Landing this issue tightens one speci
ic corner and gives reviewers a clear di

to reason about rather than a general "cleanup" commit. It should be scoped small enough to close in a single PR.��## Acceptance criteria��- [ ] The change matches the summary above.�- [ ] Tests cover the new behavior (happy path + one e
plicit
ailure mode).�- [ ] Lint, type-check, and tests all pass locally.�- [ ] PR description re
erences this issue with Closes #<this-issue>.��## Implementation hints��- Behavior must not change — the di

should be a no-op at runtime.�- E
isting tests should continue to pass without modi
ication.�- I
a rename is needed, do it in a separate commit so review is easier.��## Repo-speci
ic notes��- Ne
t.js/TypeScript app. Install with npm ci, veri
y with npm run lint, npm run typecheck, npm test.�- Money amounts must
low as integer minor units through the UI — never as
loats.�- Localization is React-Intl based; every user-
acing string must have a de ineMessage entry.�- Pre
er the e
isting useMoney() hook
or
ormatting; do not re-implement Intl.NumberFormat inline.��## Out o
scope��- Unrelated re
actors in adjacent
iles.�- Stylistic-only changes (
ormatting, renaming) that are not required by the
i
.�- Anything beyond the acceptance criteria above; sur
ace
ollow-ups as separate issues.��## How to claim and submit��
. Comment on this issue saying you'd like to take it on; wait
or a maintainer to assign you (avoids duplicated e

ort).�2. Open a PR that re
erences this issue (Closes #<this-issue>).�3. Make sure CI is green and request review
rom a CODEOWNERS maintainer.�4. PRs that close this issue and pass review may quali
y
or a reward — see the MAYBE REWARDED label and the FWC26 campaign page.��---��Category: re actor  ·  Campaign: GrantFo
OSS · O

icial Campaign | FWC26 · Maybe Rewarded

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions