Handling input fields in React - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the useState hook when handling input fields in React?

The useState hook stores the current value of the input field and allows React to update the UI when the input changes.

beginner

How do you update the state when a user types in an input field?

You use an onChange event handler that calls the state setter function with the new input value.

intermediate

What does it mean for an input field to be a "controlled component" in React?

A controlled component is an input element whose value is controlled by React state, so the displayed value always matches the state.

beginner

Why should you use the value attribute on input fields in React?

Using the value attribute links the input's displayed value to React state, ensuring the UI updates correctly and stays in sync.

intermediate

What is a common mistake when handling input fields that can cause the input to become uneditable?

Not updating the state on onChange can cause the input to be stuck because React controls the value but never changes it.

Which React hook is commonly used to store the value of an input field?

A useContext

B useEffect

C useRef

D useState

The useState hook is used to store and update the input field's value.

What event handler updates the state when a user types in an input field?

A onChange

B onSubmit

C onClick

D onFocus

The onChange event handler captures input changes and updates the state.

What happens if you set the input's value from state but do not update the state on input change?

A Input becomes uneditable

B Input clears automatically

C Input accepts input normally

D Input triggers an error

Without updating state on change, React controls the input value but never changes it, making it uneditable.

What is a controlled input in React?

A Input with no value attribute

B Input that updates DOM directly

C Input whose value is managed by React state

D Input that uses refs to get value

Controlled inputs have their value managed by React state to keep UI and data in sync.

Why is it important to link the input's value to React state?

A To prevent user typing

B To keep UI and data synchronized

C To disable the input field

D To make input read-only

Linking value to state ensures the UI shows the current data and updates correctly.

Explain how to create a controlled input field in React and why it is useful.

Think about how React controls the input's displayed value.

Describe a common mistake when handling input fields in React and how to fix it.

What happens if React controls the input but never changes the value?

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