From 68f5ceeb46caa8c8564edf2e422164af555dac6d Mon Sep 17 00:00:00 2001 From: Shuaib Hasan Akib Date: Fri, 21 Nov 2025 17:13:27 +0600 Subject: [PATCH] docs: fix incorrect Signal Forms link Updated outdated link guide/forms/signal-forms/ to the correct path guide/forms/signals/ to ensure proper navigation. Fixes: #65461 #65462 --- adev/src/content/guide/forms/signals/comparison.md | 2 +- .../src/content/guide/forms/signals/custom-controls.md | 8 ++++---- .../guide/forms/signals/field-state-management.md | 4 ++-- adev/src/content/guide/forms/signals/models.md | 10 +++++----- adev/src/content/guide/forms/signals/overview.md | 10 +++++----- adev/src/content/guide/forms/signals/validation.md | 8 ++++---- .../signal-forms/steps/6-next-steps/README.md | 10 +++++----- 7 files changed, 26 insertions(+), 26 deletions(-) diff --git a/adev/src/content/guide/forms/signals/comparison.md b/adev/src/content/guide/forms/signals/comparison.md index 209e70e06e1..d2690a92981 100644 --- a/adev/src/content/guide/forms/signals/comparison.md +++ b/adev/src/content/guide/forms/signals/comparison.md @@ -158,6 +158,6 @@ TypeScript understands your component properties but has no knowledge of form st To learn more about each approach: -- **Signal Forms**: See the [Overview guide](guide/forms/signal-forms/overview) to get started, or dive into [Form Models](guide/forms/signal-forms/models), [Validation](guide/forms/signal-forms/validation), and [Field State Management](guide/forms/signal-forms/field-state-management) +- **Signal Forms**: See the [Overview guide](guide/forms/signals/overview) to get started, or dive into [Form Models](guide/forms/signals/models), [Validation](guide/forms/signals/validation), and [Field State Management](guide/forms/signals/field-state-management) - **Reactive Forms**: See the [Reactive Forms guide](guide/forms/reactive-forms) in Angular documentation - **Template-driven Forms**: See the [Template-driven Forms guide](guide/forms/template-driven-forms) in Angular documentation diff --git a/adev/src/content/guide/forms/signals/custom-controls.md b/adev/src/content/guide/forms/signals/custom-controls.md index ba33ed4f544..1ce7026b0f7 100644 --- a/adev/src/content/guide/forms/signals/custom-controls.md +++ b/adev/src/content/guide/forms/signals/custom-controls.md @@ -241,7 +241,7 @@ export class MyForm { } ``` -TIP: For complete coverage of creating and managing form models, see the [Form Models guide](guide/forms/signal-forms/models). +TIP: For complete coverage of creating and managing form models, see the [Form Models guide](guide/forms/signals/models). When you bind `[field]="userForm.username"`, the Field directive: @@ -422,7 +422,7 @@ accountForm = form(this.accountModel, schemaPath => { This guide covered building custom controls that integrate with Signal Forms. Related guides explore other aspects of Signal Forms: -- [Form Models guide](guide/forms/signal-forms/models) - Creating and updating form models +- [Form Models guide](guide/forms/signals/models) - Creating and updating form models - - + + diff --git a/adev/src/content/guide/forms/signals/field-state-management.md b/adev/src/content/guide/forms/signals/field-state-management.md index f831a4d6793..be707bdbec8 100644 --- a/adev/src/content/guide/forms/signals/field-state-management.md +++ b/adev/src/content/guide/forms/signals/field-state-management.md @@ -47,7 +47,7 @@ In this example, the template checks `registrationForm.email().invalid()` to det ### Field state signals -The most commonly used signal is `value()`, a [writable signal](guide/forms/signal-forms/models#updating-models) that provides access to the field's current value: +The most commonly used signal is `value()`, a [writable signal](guide/forms/signals/models#updating-models) that provides access to the field's current value: ```ts const emailValue = registrationForm.email().value() @@ -691,5 +691,5 @@ Checking both `touched()` and validation state ensures styles only appear after Here are other related guides on Signal Forms: -- [Form Models guide](guide/forms/signal-forms/models) - Creating models and updating values +- [Form Models guide](guide/forms/signals/models) - Creating models and updating values - Validation guide - Defining validation rules and custom validators (coming soon) diff --git a/adev/src/content/guide/forms/signals/models.md b/adev/src/content/guide/forms/signals/models.md index 92a871918ae..64cd1dabd78 100644 --- a/adev/src/content/guide/forms/signals/models.md +++ b/adev/src/content/guide/forms/signals/models.md @@ -172,7 +172,7 @@ Field state provides reactive signals for each field's value, making it suitable TIP: Field state includes many more signals beyond `value()`, such as validation state (e.g., valid, invalid, errors), interaction tracking (e.g., touched, dirty), and visibility (e.g., hidden, disabled). - + ## Updating form models programmatically @@ -419,7 +419,7 @@ orderForm.items[0].quantity // FieldTree Array items containing objects automatically receive tracking identities, which helps maintain field state even when items change position in the array. This ensures validation state and user interactions persist correctly when arrays are reordered. - + ## Model design best practices @@ -530,7 +530,7 @@ For forms that always start with existing data, you might wait to render the for diff --git a/adev/src/content/guide/forms/signals/overview.md b/adev/src/content/guide/forms/signals/overview.md index fea36bd132c..73102a101fe 100644 --- a/adev/src/content/guide/forms/signals/overview.md +++ b/adev/src/content/guide/forms/signals/overview.md @@ -20,7 +20,7 @@ Signal Forms address these challenges by: Signal Forms work best in new applications built with signals. If you're working with an existing application that uses reactive forms, or if you need production stability guarantees, reactive forms remain a solid choice. - + ## Prerequisites @@ -52,8 +52,8 @@ To learn more about how Signal Forms work, check out the following guides: - - - - + + + + --> diff --git a/adev/src/content/guide/forms/signals/validation.md b/adev/src/content/guide/forms/signals/validation.md index aeddf0c0865..63ba327a94b 100644 --- a/adev/src/content/guide/forms/signals/validation.md +++ b/adev/src/content/guide/forms/signals/validation.md @@ -299,7 +299,7 @@ When validation rules fail, they produce error objects that describe what went w +NOTE: This section covers the errors that validation rules produce. For displaying and using validation errors in your UI, see the [Field State Management guide](guide/forms/signals/field-state-management). --> ### Error structure @@ -374,7 +374,7 @@ signupForm = form(this.signupModel, (schemaPath) => { If the email field is empty, only the `required()` error appears. If the user types "a@b", both `email()` and `minLength()` errors appear. All validation rules run - validation doesn't stop after the first failure. -TIP: Use the `touched() && invalid()` pattern in your templates to prevent errors from appearing before users have interacted with a field. For comprehensive guidance on displaying validation errors, see the [Field State Management guide](guide/forms/signal-forms/field-state-management#conditional-error-display). +TIP: Use the `touched() && invalid()` pattern in your templates to prevent errors from appearing before users have interacted with a field. For comprehensive guidance on displaying validation errors, see the [Field State Management guide](guide/forms/signals/field-state-management#conditional-error-display). ## Custom validation rules @@ -624,6 +624,6 @@ The `valid()` signal returns `false` while validation is pending, even if there This guide covered creating and applying validation rules. Related guides explore other aspects of Signal Forms: -- [Form Models guide](guide/forms/signal-forms/models) - Creating and updating form models +- [Form Models guide](guide/forms/signals/models) - Creating and updating form models - + diff --git a/adev/src/content/tutorials/signal-forms/steps/6-next-steps/README.md b/adev/src/content/tutorials/signal-forms/steps/6-next-steps/README.md index aca9ea0d78f..d50c4c20bd5 100644 --- a/adev/src/content/tutorials/signal-forms/steps/6-next-steps/README.md +++ b/adev/src/content/tutorials/signal-forms/steps/6-next-steps/README.md @@ -18,12 +18,12 @@ Ready to learn more? Here are recommended next steps: ### Explore the documentation -- **[Signal Forms Overview](guide/forms/signal-forms)** - Introduction to Signal Forms and when to use them -- **[Form Models Guide](guide/forms/signal-forms/models)** - Deep dive into form models and data management +- **[Signal Forms Overview](guide/forms/signals/overview)** - Introduction to Signal Forms and when to use them +- **[Form Models Guide](guide/forms/signals/models)** - Deep dive into form models and data management - + ## Keep learning