File tree Expand file tree Collapse file tree 1 file changed +4
-4
lines changed
adev/src/content/guide/forms/signals Expand file tree Collapse file tree 1 file changed +4
-4
lines changed Original file line number Diff line number Diff line change @@ -14,7 +14,7 @@ Form models solve this by centralizing form data in a single writable signal. Wh
1414
1515A form model is a writable signal created with Angular's ` signal() ` function. The signal holds an object that represents your form's data structure.
1616
17- ``` ts
17+ ``` angular- ts
1818import { Component, signal } from '@angular/core'
1919import { form, Field } from '@angular/forms/signals'
2020
@@ -150,7 +150,7 @@ Each field in the field tree is a function. Calling a field returns a `FieldStat
150150
151151Access field state when working with individual fields in templates or reactive computations:
152152
153- ``` ts
153+ ``` angular- ts
154154@Component({
155155 template: `
156156 <p>Current email: {{ loginForm.email().value() }}</p>
@@ -292,7 +292,7 @@ This synchronization happens automatically. You don't write subscriptions or eve
292292
293293### Example: Both directions
294294
295- ``` ts
295+ ``` angular- ts
296296@Component({
297297 template: `
298298 <input type="text" [field]="userForm.name" />
@@ -386,7 +386,7 @@ userForm.settings.theme // FieldTree<string>
386386
387387In templates, you bind nested fields the same way as top-level fields:
388388
389- ``` ts
389+ ``` angular- ts
390390@Component({
391391 template: `
392392 <input [field]="userForm.profile.firstName" />
You can’t perform that action at this time.
0 commit comments