Form validation in Svelte - Step-by-Step Execution

Concept Flow - Form validation

User inputs data

↓

Input event triggers validation

↓

Check if input meets rules

↓

Mark valid

↓

Enable submit

↓

User submits form

↓

Process valid data

The form listens to user input, checks if the data is valid, shows errors if not, and enables submission only when all inputs are valid.

Execution Sample

Svelte

let email = '';
let error = '';

function validate() {
  error = email.includes('@') ? '' : 'Invalid email';
}

This code checks if the email contains '@' and sets an error message if not.

Execution Table

Step	email value	Validation condition	error value	Submit enabled
1	'' (empty)	'' includes '@'? False	'Invalid email'	No
2	'userexample.com'	'userexample.com' includes '@'? False	'Invalid email'	No
3	'[e-mail]'	'[e-mail]' includes '@'? True	'' (no error)	Yes
4	User clicks submit	All inputs valid? True	'' (no error)	Yes

💡 Form submission only allowed when validation passes (error is empty).

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4
email	''	''	'userexample.com'	'[e-mail]'	'[e-mail]'
error	''	'Invalid email'	'Invalid email'	''	''
submitEnabled	false	false	false	true	true

Key Moments - 2 Insights

Why does the submit button stay disabled even after typing something?

Because the validation checks if the email contains '@'. Until that condition is true (see Step 3 in execution_table), the error remains and submit stays disabled.

What happens if the user fixes the email after an error?

The error message clears (Step 3), and submit becomes enabled. The form reacts immediately to input changes.

Visual Quiz - 3 Questions

Look at the execution_table, what is the error value at Step 2?

A 'Email required'

B '' (no error)

C 'Invalid email'

D 'Email too short'

💡 Hint

Check the 'error value' column at Step 2 in the execution_table.

At which step does the submit button become enabled?

A Step 3

B Step 1

C Step 2

D Step 4

💡 Hint

Look at the 'Submit enabled' column in the execution_table.

If the email never contains '@', what will happen to the submit button?

A It will become enabled after some time

B It will stay disabled forever

C It will enable only after clicking submit

D It will show a different error

💡 Hint

Refer to the validation condition and submit enabled columns in the execution_table.

Concept Snapshot

Form validation in Svelte:
- Use variables to track input and error messages.
- Validate input on change (e.g., check if email includes '@').
- Show error messages when invalid.
- Enable submit button only when all inputs are valid.
- Reactivity updates UI instantly.

Full Transcript

Form validation in Svelte works by watching user input and checking if it meets rules like containing '@' for emails. When input changes, validation runs and sets error messages if needed. The submit button is disabled if there are errors. Once input is valid, errors clear and submit enables. This flow ensures users fix mistakes before submitting.

Practice

1. What is the main purpose of form validation in a Svelte application?

easy

A. To check user input before sending data

B. To style the form elements

C. To load data from the server

D. To create new components

Solution

1. Step 1: Understand form validation role

   Form validation ensures user input is correct before submission.

2. Step 2: Identify the correct purpose

   Checking input prevents errors and improves user experience.

3. Final Answer:

   To check user input before sending data -> Option A

4. Quick Check:

   Form validation = check input [OK]

Hint: Validation means checking input before sending [OK]

Common Mistakes:

• Confusing validation with styling
• Thinking validation loads data
• Mixing validation with component creation

2. Which Svelte syntax correctly binds an input's value for validation?

easy

A.

B.

C.

D.

Solution

1. Step 1: Recall Svelte binding syntax

   Svelte uses bind:value={variable} to bind input values.

2. Step 2: Identify correct syntax

   <input bind:value={name} /> uses correct curly braces and binding keyword.

3. Final Answer:

   <input bind:value={name} /> -> Option B

4. Quick Check:

   bind:value with braces = correct [OK]

Hint: Use bind:value with curly braces for binding [OK]

Common Mistakes:

• Omitting curly braces
• Using colon instead of equals
• Using value= instead of bind:value=

3. What will be the output when submitting this Svelte form if the input is empty?

<script>
  let email = '';
  let error = '';
  function validate() {
    if (!email) {
      error = 'Email is required';
    } else {
      error = '';
    }
  }
</script>

<form on:submit|preventDefault={validate}>
  <input bind:value={email} type="email" />
  <button type="submit">Submit</button>
  <p>{error}</p>
</form>

medium

A. Error message 'Email is required' is shown

B. Form submits with no error message

C. Syntax error prevents form rendering

D. Form reloads the page

Solution

1. Step 1: Analyze validation function

   If email is empty, error is set to 'Email is required'.

2. Step 2: Check form submission behavior

   Submit event is prevented from default, so page does not reload, and error message shows.

3. Final Answer:

   Error message 'Email is required' is shown -> Option A

4. Quick Check:

   Empty input triggers error message [OK]

Hint: Empty input triggers error message display [OK]

Common Mistakes:

• Ignoring preventDefault causing page reload
• Expecting form to submit without error
• Confusing syntax error with logic error

4. Identify the error in this Svelte form validation code:

<script>
  let password = '';
  let error = '';
  function check() {
    if(password.length < 6) {
      error = 'Password too short';
    }
  }
</script>

<form on:submit={check}>
  <input bind:value={password} type="password" />
  <button type="submit">Login</button>
  <p>{error}</p>
</form>

medium

A. Incorrect binding syntax for password

B. Error message variable not declared

C. Missing preventDefault on submit event

D. Password length check uses wrong operator

Solution

1. Step 1: Review submit event handling

   The form's submit event calls check but does not prevent default, so page reloads.

2. Step 2: Identify missing preventDefault

   Without preventDefault, error message disappears on reload, breaking validation UX.

3. Final Answer:

   Missing preventDefault on submit event -> Option C

4. Quick Check:

   Submit needs preventDefault to stop reload [OK]

Hint: Always use preventDefault on form submit to keep validation visible [OK]

Common Mistakes:

• Forgetting preventDefault causes page reload
• Thinking binding syntax is wrong when it is correct
• Assuming error variable is missing

5. How can you improve accessibility when showing validation errors in a Svelte form?

hard

A. Remove labels to reduce clutter

B. Use only color changes to show errors

C. Hide error messages visually but keep them in the DOM

D. Add aria-live="polite" to error message container

Solution

1. Step 1: Understand accessibility for errors

   Screen readers need to be notified of error changes dynamically.

2. Step 2: Use aria-live attribute

   Adding aria-live="polite" tells assistive tech to announce updates politely.

3. Final Answer:

   Add aria-live="polite" to error message container -> Option D

4. Quick Check:

   aria-live improves screen reader announcements [OK]

Hint: Use aria-live for dynamic error announcements [OK]

Common Mistakes:

• Relying only on color changes (not accessible)
• Hiding errors visually removes info from users
• Removing labels harms form clarity