You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: blog/2025-10-signal-forms-part1/README.md
+9-5Lines changed: 9 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: "Angular Signal Forms Part 1: Getting Started with the Basics"
3
3
author: Danny Koppenhagen and Ferdinand Malcher
4
4
mail: dannyferdigravatar@fmalcher.de # Gravatar
5
5
published: 2025-10-13
6
-
lastModified: 2025-10-15
6
+
lastModified: 2025-10-16
7
7
keywords:
8
8
- Angular
9
9
- Signals
@@ -479,7 +479,7 @@ To make the error display reusable, we can create a dedicated component for it:
479
479
The component can receive any `FieldTree` and checks for its errors when the field is already marked as touched.
480
480
It displays all errors related to the field by iterating over the `errors()` signal.
481
481
482
-
To get access to the `FieldState`, we have to call the `field` property twice: Once to get the `FieldTree` from the input signal, and a second time to get the `FieldState` with its reactive properties.
482
+
To get access to the `FieldState`, we have to call the `fieldRef` property twice: Once to get the `FieldTree` from the input signal, and a second time to get the `FieldState` with its reactive properties.
0 commit comments