Form validation patterns in Remix - Mini Project: Build & Apply

Form validation patterns

📖 Scenario: You are building a simple signup form for a website using Remix. The form should collect a user's username and email. You want to make sure the user enters a username and a valid email before submitting.

🎯 Goal: Create a Remix form with two input fields: username and email. Add basic validation to check that the username is not empty and the email contains an '@' symbol. Show error messages if validation fails.

📋 What You'll Learn

Create a Remix form with username and email input fields

Add a validation function to check username is not empty

Add a validation function to check email contains '@'

Display error messages below each input if validation fails

Use Remix action function to handle form submission and validation

💡 Why This Matters

🌍 Real World

Forms are everywhere on websites and apps. Validating user input ensures data quality and prevents errors.

💼 Career

Understanding form validation in Remix is important for building reliable web applications and improving user experience.

1

Set up initial form data

Create a variable called formData as an object with keys username and email, both set to empty strings.

Remix

# Create formData object with username and email as empty strings
# Your code here

Hint

Think of formData as a box holding the values typed in the form fields.

2

Add validation rules

Create a function called validateForm that takes formData as input and returns an object called errors. Add these rules: if username is empty, add errors.username = 'Username is required'. If email does not include '@', add errors.email = 'Email must include @'.

Remix

const formData = { username: '', email: '' };

// Create validateForm function to check username and email
# Your code here

Hint

Use simple if checks and return an object with error messages.

3

Implement Remix action for form submission

Create an async function called action that takes { request } as argument. Inside, get form data using await request.formData(). Extract username and email from the form data. Use validateForm to get errors. If errors has any keys, return them as JSON. Otherwise, return a success message as JSON.

Remix

const formData = { username: '', email: '' };

function validateForm(formData) {
  const errors = {};
  if (!formData.username) {
    errors.username = 'Username is required';
  }
  if (!formData.email.includes('@')) {
    errors.email = 'Email must include @';
  }
  return errors;
}

// Create async action function to handle form submission
# Your code here

Hint

Use Remix's action function to process form data and return validation results.

4

Build the form component with error display

Create a default exported React function component called SignupForm. Inside, use useActionData() to get actionData. Render a <form method='post'> with two inputs: username and email. Below each input, if actionData?.errors?.username or actionData?.errors?.email exist, show them in a <div> with role='alert'. Add a submit button labeled 'Sign Up'.

Remix

const formData = { username: '', email: '' };

function validateForm(formData) {
  const errors = {};
  if (!formData.username) {
    errors.username = 'Username is required';
  }
  if (!formData.email.includes('@')) {
    errors.email = 'Email must include @';
  }
  return errors;
}

export async function action({ request }) {
  const form = await request.formData();
  const username = form.get('username') || '';
  const email = form.get('email') || '';
  const errors = validateForm({ username, email });
  if (Object.keys(errors).length) {
    return { errors };
  }
  return { success: true };
}

// Create SignupForm component with form and error messages
# Your code here

Hint

Use useActionData() to get errors and show them below inputs with role='alert' for accessibility.

Practice

1. What is the main purpose of form validation in Remix Framework?

easy

A. To check user input and ensure data is correct before processing

B. To style the form elements with CSS

C. To load external scripts for the form

D. To create new database tables automatically

Solution

1. Step 1: Understand form validation role

   Form validation checks if user input meets rules to avoid errors.

2. Step 2: Identify Remix usage

   Remix uses validation to keep data correct and improve user experience.

3. Final Answer:

   To check user input and ensure data is correct before processing -> Option A

4. Quick Check:

   Form validation = check input correctness [OK]

Hint: Validation means checking input correctness before saving [OK]

Common Mistakes:

• Confusing validation with styling
• Thinking validation creates database tables
• Assuming validation loads scripts

2. Which syntax correctly defines an action function in Remix for form validation?

easy

A. async function action(request) { return 'ok'; }

B. function action() { return 'done'; }

C. export function loader() { return 'load'; }

D. export async function action({ request }) { const formData = await request.formData(); return null; }

Solution

1. Step 1: Identify Remix action signature

   Remix action is an async exported function receiving an object with request.

2. Step 2: Check correct syntax

   export async function action({ request }) { const formData = await request.formData(); return null; } matches the correct async export with destructured request and formData usage.

3. Final Answer:

   export async function action({ request }) { const formData = await request.formData(); return null; } -> Option D

4. Quick Check:

   Correct action syntax = async export with { request } [OK]

Hint: Action must be async export with { request } parameter [OK]

Common Mistakes:

• Using loader instead of action
• Missing async keyword
• Not destructuring request from parameter

3. Given this Remix action code, what will be the response if the email field is empty?

export async function action({ request }) {
  const formData = await request.formData();
  const email = formData.get('email');
  if (!email) {
    return json({ error: 'Email is required' }, { status: 400 });
  }
  return json({ success: true });
}

medium

A. A JSON response with { success: true } and status 200

B. A JSON response with { error: 'Email is required' } and status 400

C. A runtime error because email is undefined

D. Redirect to another page

Solution

1. Step 1: Check email validation condition

   If email is empty or falsy, the code returns a JSON error with status 400.

2. Step 2: Understand response when email missing

   Since email is empty, the condition triggers and returns error JSON with status 400.

3. Final Answer:

   A JSON response with { error: 'Email is required' } and status 400 -> Option B

4. Quick Check:

   Empty email triggers error JSON with 400 status [OK]

Hint: Empty input triggers error JSON with status 400 [OK]

Common Mistakes:

• Assuming success response when input is empty
• Thinking it throws runtime error
• Confusing JSON response with redirect

4. Identify the error in this Remix action function for validating a password length:

export async function action({ request }) {
  const formData = await request.formData();
  const password = formData.get('password');
  if (password.length < 8) {
    return json({ error: 'Password too short' }, { status: 400 });
  }
  return json({ success: true });
}

medium

A. The function should be named loader, not action

B. json function is not imported

C. password might be null, causing .length to throw an error

D. The status code 400 is incorrect for validation errors

Solution

1. Step 1: Check password retrieval and usage

   formData.get returns null if field missing, so password could be null.

2. Step 2: Analyze .length usage on password

   Calling .length on null causes runtime error; must check password exists first.

3. Final Answer:

   password might be null, causing .length to throw an error -> Option C

4. Quick Check:

   Null password causes .length error [OK]

Hint: Check if password exists before using .length [OK]

Common Mistakes:

• Ignoring null possibility from formData.get
• Assuming json is always imported
• Confusing action with loader function

5. How can you combine server-side validation with client-side feedback in Remix to improve form UX?

hard

A. Use the action function to validate and return JSON errors, then display errors in the form component

B. Only validate on the client side using JavaScript event listeners

C. Skip validation and rely on database constraints

D. Use a separate API endpoint unrelated to the form

Solution

1. Step 1: Understand Remix validation flow

   Remix uses the action function on server to validate and return JSON errors.

2. Step 2: Connect server errors to client UI

   Returned JSON errors can be shown in the form component to give user feedback.

3. Final Answer:

   Use the action function to validate and return JSON errors, then display errors in the form component -> Option A

4. Quick Check:

   Server validation + client error display = better UX [OK]

Hint: Validate server-side, show errors client-side for best UX [OK]

Common Mistakes:

• Relying only on client-side validation
• Ignoring server validation errors
• Using unrelated API endpoints for validation