aws-amplify / aws-amplify/amplify-ui

[FR] Ability to tell if form is dirty when adding custom sign up fields

Open
#5,754 2 comments 0 reactions 0 assignees View on GitHub
Authenticator feature-request
Dominant language
TypeScript
Stars
1.1k
Forks
347
Avg merge
18h 29m
Merged PRs (30d)
9

Description

### On which framework/platform would you like to see this feature implemented?

React

### Which UI component is this feature-request for?

Authenticator

### Please describe your feature-request in detail.

We are implementing an "Agree to terms" checkbox on sign up following the example listed in your docs (https://ui.docs.amplify.aws/react/connected-components/authenticator/customization#sign-up-fields).

We noticed that the error message is showing up before the form is submitted, and we would like to have a way to only show the error message is the form is "dirty".

### Please describe a solution you'd like.

_No response_

### We love contributors! Is this something you'd be interested in working on?

- [ ] 👋 I may be able to implement this feature request.
- [ ] ⚠️ This feature might incur a breaking change.

Contributor guide

Open the contributing guide

Research direction

Start with the React Authenticator custom sign-up-fields example in the linked documentation and reproduce the Agree to terms checkbox behavior. Trace when its validation error appears relative to form submission, and define completion as showing that error only once the form is dirty. Verify the behavior in the Authenticator sign-up flow.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
authentication, frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.