title: Basic Signal Form

summary: Creates a reactive link between a WritableSignal data model and native HTML inputs using the `form()` function and `[control]` directive.

keywords:

- signal forms

- form

- control

- basic example

- submit

required_packages:

- '@angular/forms'

related_concepts:

- 'signals'

The purpose of this pattern is to create a reactive, two-way link between a component's data model and its template. The problem it solves is keeping the state of the UI (the form inputs) perfectly synchronized with the application's state (the signal model) without manual state management, ensuring data consistency at all times.

Use this pattern as the starting point for any new form in an Angular application. It is the modern, preferred way to handle forms, superseding the traditional `FormsModule` (`NgModel`) and `ReactiveFormsModule` (`FormGroup`, `FormControl`) for most use cases by offering better type safety and a more reactive, signal-based architecture.

- **`form()`:** A function that creates a `Field` representing the form, taking a `WritableSignal` as the data model.

- **`[control]` directive:** Binds a `Field` from your component to a native HTML input element, creating a two-way data binding.

- **`submit()`:** An async helper function that manages the form's submission state and should be called from the submit event handler.

This example consists of a standalone component that defines and manages a user profile form.

This file defines the component's logic, including the signal-based data model and the form structure.

import { Component, signal, Output, EventEmitter, ChangeDetectionStrategy } from '@angular/core';

import { form, submit } from '@angular/forms/signals';

import { JsonPipe } from '@angular/common';

export interface UserProfile {

firstName: string;

lastName: string;

email: string;

}

@Component({

selector: 'app-user-profile',

standalone: true,

imports: [JsonPipe],

templateUrl: './user-profile.component.html',

changeDetection: ChangeDetectionStrategy.OnPush,

})

export class UserProfileComponent {

@Output() submitted = new EventEmitter<UserProfile>();

profileModel = signal<UserProfile>({

firstName: '',

lastName: '',

email: '',

});

profileForm = form(this.profileModel);

async handleSubmit() {

// For this basic example, we assume the form is always valid for submission.

// See the validation example for how to handle invalid forms.

await submit(this.profileForm, async () => {

this.submitted.emit(this.profileForm().value());

});

}

}

The template is wrapped in a `<form>` tag with a `(submit)` event and a submit button.

<form (submit)="handleSubmit(); $event.preventDefault()">

<div>

<label>

First Name:

<input type="text" [control]="profileForm.firstName" />

</label>

</div>

<div>

<label>

Last Name:

<input type="text" [control]="profileForm.lastName" />

</label>

</div>

<div>

<label>

Email:

<input type="email" [control]="profileForm.email" />

</label>

</div>

<button type="submit">Submit</button>

</form>

<h3>Live Form Value:</h3>

<pre>{{ profileForm().value() | json }}</pre>

- The `[control]` directive automatically handles the two-way data binding between the input element and the corresponding `Field` in the `profileForm`.

- The `profileForm()` signal gives you access to the `FieldState`, which includes the form's `value` as a signal.

- The native `(submit)` event on the `<form>` element is bound to the `handleSubmit` method. It's important to call `$event.preventDefault()` to prevent a full page reload.

- The `handleSubmit` method uses the `submit()` helper to manage the submission process.

The parent component imports the `UserProfile` interface and listens for the `(submitted)` event to receive the strongly-typed form data.

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

import { JsonPipe } from '@angular/common';

import { UserProfileComponent, UserProfile } from './user-profile.component';

@Component({

selector: 'app-root',

standalone: true,

imports: [UserProfileComponent, JsonPipe],

template: `

`,

})

export class AppComponent {

submittedData: UserProfile | null = null;

onProfileSubmit(data: UserProfile) {

this.submittedData = data;

console.log('Profile data submitted:', data);

}

}

title: Signal Form with Built-in Validators

summary: Demonstrates how to use the suite of built-in validators like `required`, `minLength`, `email`, and `pattern` within a signal form schema.

keywords:

- signal forms

- validation

- built-in validators

- required

- minLength

- maxLength

- min

- max

- email

- pattern

- schema

required_packages:

- '@angular/forms'

related_concepts:

- 'signals'

The purpose of this pattern is to apply common, standard validation rules to form fields with minimal boilerplate. It solves the problem of repeatedly implementing frequent checks (e.g., for required fields, email formats, or length constraints) by providing a pre-built, configurable, and optimized set of validators.

Use this pattern as the primary method for applying common validation logic in your signal forms. These built-in functions should be your first choice before writing custom validators, as they cover the vast majority of real-world validation scenarios. They are the modern, signal-based equivalent of the static methods on the `Validators` class from `@angular/forms`.

- **`required()`:** A built-in validator that ensures a field has a value.

- **`minLength(number)`:** A built-in validator that ensures a string's length is at least the specified minimum.

- **`email()`:** A built-in validator that checks if a string is in a valid email format.

- **`submit()`:** An async helper function that manages the form's submission state and should be called from the submit event handler.

This example consists of a standalone component that defines and manages a user settings form with built-in validators.

This file defines the component's logic, including the data model and a validation schema that uses multiple built-in validators.

import { Component, signal, Output, EventEmitter, ChangeDetectionStrategy } from '@angular/core';

import { form, schema, submit } from '@angular/forms/signals';

import { required, minLength, maxLength, min, max, email, pattern } from '@angular/forms/signals';

import { JsonPipe } from '@angular/common';

export interface UserSettings {

username: string;

age: number;

email: string;

website: string;

}

const settingsSchema = schema<UserSettings>((form) => {

required(form.username);

minLength(form.username, 3);

maxLength(form.username, 20);

required(form.age);

min(form.age, 18);

max(form.age, 100);

required(form.email);

email(form.email);

pattern(form.website, /^(https?:\/\/)?([\da-z\.-]+)\.([a-z\.]{2,6})([\/\w \.-]*)*\/?$/);

});

@Component({

selector: 'app-user-settings',

standalone: true,

imports: [JsonPipe],

templateUrl: './user-settings.component.html',

changeDetection: ChangeDetectionStrategy.OnPush,

})

export class UserSettingsComponent {

@Output() submitted = new EventEmitter<UserSettings>();

settingsModel = signal<UserSettings>({

username: '',

age: 18,

email: '',

website: '',

});

settingsForm = form(this.settingsModel, settingsSchema);

async handleSubmit() {

await submit(this.settingsForm, async () => {

this.submitted.emit(this.settingsForm().value());

});

}

}

This file provides the template for the form, displaying specific error messages for each potential validation failure.

<form (submit)="handleSubmit(); $event.preventDefault()">

<div>

<label>Username:</label>

<input type="text" [control]="settingsForm.username" />

@if (settingsForm.username().errors().length > 0) {

<div class="errors">

@for (error of settingsForm.username().errors()) { @switch (error.kind) { @case ('required') {

<p>Username is required.</p>

} @case ('minLength') {

<p>Username must be at least 3 characters.</p>

} @case ('maxLength') {

<p>Username cannot exceed 20 characters.</p>

} } }

</div>

}

</div>

<div>

<label>Age:</label>

<input type="number" [control]="settingsForm.age" />

@if (settingsForm.age().errors().length > 0) {

<div class="errors">

@for (error of settingsForm.age().errors()) { @switch (error.kind) { @case ('required') {

<p>Age is required.</p>

} @case ('min') {

<p>You must be at least 18 years old.</p>

} @case ('max') {

<p>Age cannot be more than 100.</p>

} } }

</div>

}

</div>

<div>

<label>Email:</label>

<input type="email" [control]="settingsForm.email" />

@if (settingsForm.email().errors().length > 0) {

<div class="errors">

@for (error of settingsForm.email().errors()) { @switch (error.kind) { @case ('required') {

<p>Email is required.</p>

} @case ('email') {

<p>Please enter a valid email address.</p>

} } }

</div>

}

</div>

<div>

<label>Website:</label>

<input type="url" [control]="settingsForm.website" />

@if (settingsForm.website().errors().length > 0) {

<div class="errors">

@for (error of settingsForm.website().errors()) { @switch (error.kind) { @case ('pattern') {

<p>Please enter a valid URL.</p>

} } }

</div>

}

</div>

<button type="submit" [disabled]="!settingsForm().valid()">Save Settings</button>

</form>

- All built-in validators are imported directly from `@angular/forms`.

- The native `(submit)` event on the `<form>` element is bound to the `handleSubmit` method. It's important to call `$event.preventDefault()` to prevent a full page reload.

- The `handleSubmit` method uses the `submit()` helper to manage the submission process.

The parent component listens for the `(submitted)` event to receive the validated form data.

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

import { JsonPipe } from '@angular/common';

import { UserSettingsComponent, UserSettings } from './user-settings.component';

@Component({

selector: 'app-root',

standalone: true,

imports: [UserSettingsComponent, JsonPipe],

template: `

`,

})

export class AppComponent {

submittedData: UserSettings | null = null;

onFormSubmit(data: UserSettings) {

this.submittedData = data;

console.log('Settings data submitted:', data);

}

}