Form submission handling in Angular

Introduction

Form submission handling lets your app collect and use information users type in forms. It helps you respond when users click submit.

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

When you need to check if the user filled the form correctly before sending data.

When you want to show a message after the user submits a form.

When you want to save user data to a server after submission.

Syntax

Angular

import { Component } from '@angular/core';
import { FormsModule } from '@angular/forms';

@Component({
  selector: 'app-simple-form',
  standalone: true,
  imports: [FormsModule],
  template: `
    <form (ngSubmit)="onSubmit()" #formRef="ngForm">
      <input name="username" [(ngModel)]="username" required aria-label="Username" />
      <button type="submit" [disabled]="formRef.invalid">Submit</button>
    </form>
  `
})
export class SimpleFormComponent {
  username = '';

  onSubmit() {
    // handle form data here
  }
}

Use (ngSubmit) on the <form> tag to catch the submit event.

Use [(ngModel)] to bind input values to component properties.

Examples

Basic form with email input and submit button.

Angular

<form (ngSubmit)="submitForm()">
  <input name="email" [(ngModel)]="email" required aria-label="Email" />
  <button type="submit">Send</button>
</form>

Form disables submit button if input is invalid.

Angular

<form (ngSubmit)="save()" #myForm="ngForm">
  <input name="age" type="number" [(ngModel)]="age" min="1" max="120" aria-label="Age" />
  <button type="submit" [disabled]="myForm.invalid">Save</button>
</form>

Sample Program

This component shows a form with name and email fields. The submit button is disabled until both fields are valid. When submitted, it shows a thank you message with the entered data.

Angular

import { Component } from '@angular/core';
import { CommonModule } from '@angular/common';
import { FormsModule } from '@angular/forms';

@Component({
  selector: 'app-user-form',
  standalone: true,
  imports: [CommonModule, FormsModule],
  template: `
    <form (ngSubmit)="onSubmit()" #userForm="ngForm">
      <label for="name">Name:</label>
      <input id="name" name="name" [(ngModel)]="name" required aria-label="Name" />

      <label for="email">Email:</label>
      <input id="email" name="email" [(ngModel)]="email" required email aria-label="Email" />

      <button type="submit" [disabled]="userForm.invalid">Submit</button>
    </form>

    <p *ngIf="submitted">Thank you, {{ name }}! We received your email: {{ email }}.</p>
  `
})
export class UserFormComponent {
  name = '';
  email = '';
  submitted = false;

  onSubmit() {
    this.submitted = true;
  }
}

Important Notes

Always add aria-label or label elements for accessibility.

Use Angular's form validation to prevent bad data submission.

Use template reference variables like #userForm="ngForm" to check form state.

Summary

Use (ngSubmit) to handle form submission in Angular.

Bind inputs with [(ngModel)] for two-way data binding.

Disable submit button when form is invalid to improve user experience.

Practice

1. What is the purpose of the (ngSubmit) directive in Angular forms?

easy

A. It binds the form inputs to component properties.

B. It listens for the form's submit event and triggers a handler function.

C. It disables the submit button when the form is invalid.

D. It styles the form elements automatically.

Solution

1. Step 1: Understand the role of (ngSubmit)

   The (ngSubmit) directive listens for the submit event on a form element in Angular.

2. Step 2: Identify what happens on submit

   When the form is submitted, (ngSubmit) triggers the specified handler function in the component.

3. Final Answer:

   It listens for the form's submit event and triggers a handler function. -> Option B

4. Quick Check:

   (ngSubmit) handles form submission event [OK]

Hint: Remember (ngSubmit) triggers code on form submit [OK]

Common Mistakes:

• Confusing (ngSubmit) with input binding
• Thinking (ngSubmit) disables buttons
• Assuming (ngSubmit) styles forms

2. Which of the following is the correct syntax to bind an input field to a component property named username using two-way binding in Angular?

easy

A.

B.

C.

D.

Solution

1. Step 1: Recall two-way binding syntax

   Angular uses [(ngModel)] for two-way data binding on form inputs.

2. Step 2: Match syntax to property

   The correct syntax to bind username is <input [(ngModel)]="username">.

3. Final Answer:

   <input [(ngModel)]="username"> -> Option A

4. Quick Check:

   Two-way binding = [(ngModel)] [OK]

Hint: Two-way binding always uses [(ngModel)] [OK]

Common Mistakes:

• Using only [ngModel] without parentheses
• Using (ngModelChange) alone without brackets
• Confusing event binding with property binding

3. Given the following Angular template snippet, what will be the value of submittedName after the form is submitted?

<form (ngSubmit)="submitForm()" #myForm="ngForm">
  <input name="name" [(ngModel)]="userName" required>
  <button type="submit" [disabled]="myForm.invalid">Submit</button>
</form>

And the component code:

userName = '';
submittedName = '';

submitForm() {
  this.submittedName = this.userName;
}

If the user types "Alice" and submits, what is submittedName?

medium

A. undefined

B. "" (empty string)

C. "Alice"

D. null

Solution

1. Step 1: Understand two-way binding effect

   The input field binds userName with two-way binding, so typing "Alice" updates userName to "Alice".

2. Step 2: Check submitForm behavior

   On submit, submitForm() sets submittedName to the current userName, which is "Alice".

3. Final Answer:

   "Alice" -> Option C

4. Quick Check:

   Two-way binding updates userName, submitForm copies it [OK]

Hint: Two-way binding updates property before submit [OK]

Common Mistakes:

• Assuming submittedName stays empty
• Confusing variable names
• Ignoring two-way binding effect

4. Identify the error in this Angular form submission code snippet:

<form (ngSubmit)="onSubmit">
  <input [(ngModel)]="email" name="email" required>
  <button type="submit">Send</button>
</form>

Component method:

onSubmit() {
  console.log('Form submitted:', this.email);
}

medium

A. The (ngSubmit) should be (ngSubmit)="onSubmit()" with parentheses.

B. The input is missing a type attribute.

C. The button should have [disabled]="form.invalid".

D. The name attribute on input is not needed.

Solution

1. Step 1: Check (ngSubmit) syntax

   The (ngSubmit) directive requires a function call with parentheses to execute the method on submit.

2. Step 2: Identify the missing parentheses

   Using (ngSubmit)="onSubmit" passes the function reference but does not call it; it should be (ngSubmit)="onSubmit()".

3. Final Answer:

   The (ngSubmit) should be (ngSubmit)="onSubmit()" with parentheses. -> Option A

4. Quick Check:

   Call handler with () in (ngSubmit) [OK]

Hint: Always add () to call function in (ngSubmit) [OK]

Common Mistakes:

• Omitting parentheses in (ngSubmit)
• Ignoring required name attribute
• Thinking input type is mandatory for submission

5. You want to disable the submit button in an Angular form until all required fields are valid. Which approach correctly implements this behavior?

<form (ngSubmit)="submit()" #myForm="ngForm">
  <input name="email" [(ngModel)]="email" required>
  <input name="password" [(ngModel)]="password" required minlength="6">
  <button type="submit" ???>Submit</button>
</form>

What should replace ??? to disable the button when the form is invalid?

hard

A. [disabled]="email === '' || password.length < 6"

B. [disabled]="myForm.valid"

C. [disabled]="false"

D. [disabled]="myForm.invalid"

Solution

1. Step 1: Understand Angular form validity

   The template reference variable myForm exposes the form's validity state via myForm.invalid and myForm.valid.

2. Step 2: Use form invalid property to disable button

   Setting [disabled]="myForm.invalid" disables the submit button until the form is valid.

3. Final Answer:

   [disabled]="myForm.invalid" -> Option D

4. Quick Check:

   Disable button when form.invalid is true [OK]

Hint: Use form.invalid to disable submit button [OK]

Common Mistakes:

• Using negation incorrectly with valid property
• Manually checking fields instead of form state
• Setting disabled to false always