Handling input fields in React

Introduction

Handling input fields lets your app listen to what users type and respond to it. This makes your app interactive and useful.

When you want to get user information like name or email.

When you need to update something on the screen as the user types.

When you want to check or validate user input before sending it.

When you want to save user choices or preferences.

When building forms like login, signup, or search boxes.

Syntax

React

import React, { useState } from 'react';

const [value, setValue] = useState('');

<input
  type="text"
  value={value}
  onChange={e => setValue(e.target.value)}
/>

The value attribute links the input to React state.

The onChange event updates the state when the user types.

Examples

Basic text input that updates the name state as you type.

React

import React, { useState } from 'react';

const [name, setName] = useState('');

<input
  type="text"
  value={name}
  onChange={e => setName(e.target.value)}
/>

Email input with an ARIA label for accessibility.

React

import React, { useState } from 'react';

const [email, setEmail] = useState('');

<input
  type="email"
  value={email}
  onChange={e => setEmail(e.target.value)}
  aria-label="Email address"
/>

Password input hides typed characters and updates state.

React

import React, { useState } from 'react';

const [password, setPassword] = useState('');

<input
  type="password"
  value={password}
  onChange={e => setPassword(e.target.value)}
  aria-label="Password"
/>

Sample Program

This React component shows a text input for your name. As you type, it updates the greeting below in real time. It uses accessible labels and simple styling for clarity.

React

import React, { useState } from 'react';

export default function NameInput() {
  const [name, setName] = useState('');

  return (
    <main style={{ padding: '1rem', fontFamily: 'Arial, sans-serif' }}>
      <label htmlFor="nameInput" style={{ display: 'block', marginBottom: '0.5rem' }}>
        Enter your name:
      </label>
      <input
        id="nameInput"
        type="text"
        value={name}
        onChange={e => setName(e.target.value)}
        aria-label="Name input"
        style={{ padding: '0.5rem', fontSize: '1rem', width: '100%', maxWidth: '300px' }}
      />
      <p style={{ marginTop: '1rem', fontSize: '1.2rem' }}>
        Hello, {name || 'stranger'}!
      </p>
    </main>
  );
}

Important Notes

Always link the input's value to state to keep React in control.

Use aria-label or label elements for accessibility.

Remember to handle different input types like text, email, and password properly.

Summary

Handling input fields means connecting user typing to React state.

Use value and onChange to keep input and state in sync.

Accessibility and simple styling improve user experience.

Practice

1. What is the main purpose of using useState when handling input fields in React?

easy

A. To store and update the current value of the input field

B. To style the input field dynamically

C. To fetch data from an API when input changes

D. To prevent the input field from rendering

Solution

1. Step 1: Understand the role of useState

   useState is a React hook used to create state variables that can hold values and update them.

2. Step 2: Connect useState to input fields

   When handling input fields, useState stores the current input value and updates it as the user types.

3. Final Answer:

   To store and update the current value of the input field -> Option A

4. Quick Check:

   useState manages input value = A [OK]

Hint: useState holds input value and updates on change [OK]

Common Mistakes:

• Thinking useState styles the input
• Confusing useState with fetching data
• Believing useState stops rendering

2. Which of the following is the correct way to update state when handling an input field change in React?

easy

A. onChange={() => setValue(e.target.value)}

B. onChange={(e) => setValue(e.target.value)}

C. onChange={(e) => setValue(e.value)}

D. onChange={(e) => setValue(e.target)}

Solution

1. Step 1: Identify the event object usage

   The event object e contains the input element in e.target, and its value is in e.target.value.

2. Step 2: Check the correct syntax for updating state

   The state update function should be called with e.target.value inside the arrow function.

3. Final Answer:

   onChange={(e) => setValue(e.target.value)} -> Option B

4. Quick Check:

   Use e.target.value to update state [OK]

Hint: Use e.target.value inside onChange handler [OK]

Common Mistakes:

• Omitting event parameter e
• Using e.value instead of e.target.value
• Passing e.target instead of its value

3. What will be displayed when the following React component is rendered and the user types 'hello' in the input field?

import React, { useState } from 'react';

function InputExample() {
  const [text, setText] = useState('');
  return (
    <div>
      <input value={text} onChange={e => setText(e.target.value)} />
      <p>You typed: {text}</p>
    </div>
  );
}

medium

A. An input box showing 'hello' but no paragraph

B. An input box with no text and an empty paragraph

C. An input box and a paragraph showing 'You typed: hello'

D. A syntax error preventing rendering

Solution

1. Step 1: Understand controlled input behavior

   The input's value is controlled by the state variable text. Typing updates text via setText.

2. Step 2: Check rendered output

   The paragraph displays the current text value, so typing 'hello' shows 'You typed: hello'.

3. Final Answer:

   An input box and a paragraph showing 'You typed: hello' -> Option C

4. Quick Check:

   Controlled input shows typed text [OK]

Hint: Controlled input updates state and shows typed text [OK]

Common Mistakes:

• Thinking input is uncontrolled and won't update
• Expecting paragraph to be empty
• Assuming syntax error without cause

4. Identify the error in this React input handler code:

function MyInput() {
  const [value, setValue] = useState('');
  function handleChange() {
    setValue(e.target.value);
  }
  return <input value={value} onChange={handleChange} />;
}

medium

A. The event parameter e is missing in handleChange

B. The value state is not initialized

C. The onChange should be onInput

D. The input should not have a value prop

Solution

1. Step 1: Check the handleChange function signature

   handleChange uses e.target.value but does not receive e as a parameter, causing a ReferenceError.

2. Step 2: Correct the function to accept event

   Adding e as a parameter fixes the error: function handleChange(e) { setValue(e.target.value); }.

3. Final Answer:

   The event parameter e is missing in handleChange -> Option A

4. Quick Check:

   Event parameter needed in handler [OK]

Hint: Always pass event parameter to onChange handler [OK]

Common Mistakes:

• Forgetting to add event parameter e
• Using wrong event like onInput
• Removing value prop from controlled input

5. You want to create a form with two input fields, firstName and lastName, and update their values independently using a single useState object. Which code snippet correctly updates the state when either input changes?

const [form, setForm] = useState({ firstName: '', lastName: '' });

// Which onChange handler is correct?

A) onChange={e => setForm({ [e.target.name]: e.target.value })}

B) onChange={e => setForm(prev => ({ ...prev, [e.target.name]: e.target.value }))}

C) onChange={e => setForm({ form, [e.target.name]: e.target.value })}

D) onChange={e => setForm({ form: { [e.target.name]: e.target.value } })}

hard

A. Updates state but overwrites other fields, losing data

B. Wraps updated field inside another object, breaking state

C. Incorrectly nests state causing wrong structure

D. Correctly merges new field value with existing state

Solution

1. Step 1: Understand state update with objects

   When updating part of an object state, you must merge the new field with existing fields to avoid losing data.

2. Step 2: Analyze each option

   Updates state but overwrites other fields, losing data replaces the entire state with only one field, losing the other. Correctly merges new field value with existing state uses a function to merge previous state with the new field correctly. Options C and D incorrectly nest or wrap the state, breaking the structure.

3. Final Answer:

   Correctly merges new field value with existing state -> Option D

4. Quick Check:

   Use spread operator to merge state updates [OK]

Hint: Use spread ...prev to merge state updates in objects [OK]

Common Mistakes:

• Overwriting entire state object losing other fields
• Nesting state inside another object accidentally
• Not using functional update form for safety