From 3014aa5d460fa6c5e868bd80342cd4c5d405de0f Mon Sep 17 00:00:00 2001 From: Anushka Geeta Singh Date: Wed, 25 Feb 2026 00:41:55 +0530 Subject: [PATCH 1/7] docs: update README to clarify app setup confirmation Improved wording to clarify how beginners can verify their environment and IDE are correctly set up after running the app. --- .../content/tutorials/first-app/steps/01-hello-world/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/adev/src/content/tutorials/first-app/steps/01-hello-world/README.md b/adev/src/content/tutorials/first-app/steps/01-hello-world/README.md index 33cd19a7fa61..68f3c866ba6a 100644 --- a/adev/src/content/tutorials/first-app/steps/01-hello-world/README.md +++ b/adev/src/content/tutorials/first-app/steps/01-hello-world/README.md @@ -6,7 +6,7 @@ This first lesson serves as the starting point from which each lesson in this tu ## What you'll learn -The updated app you have after this lesson confirms that you and your IDE are ready to begin creating an Angular app. +If your application runs successfully in the browser and displays the executed content without errors, it confirms that your development environment and IDE are correctly set up to begin building an Angular app. NOTE: If you are working with the embedded editor, skip to [step four](#create-hello-world). When working in the browser playground, you do not need to `ng serve` to run the app. Other commands like `ng generate` can be done in the console window to your right. From 0db9fbe966fab401b2d1e8d7043df211de722add Mon Sep 17 00:00:00 2001 From: Anushka Geeta Singh Date: Thu, 26 Feb 2026 19:55:07 +0530 Subject: [PATCH 2/7] docs(signals): clarify when to use linkedSignal vs computed --- adev/src/content/guide/signals/linked-signal.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/adev/src/content/guide/signals/linked-signal.md b/adev/src/content/guide/signals/linked-signal.md index e8169d3f9d2c..ce20cf1b1521 100644 --- a/adev/src/content/guide/signals/linked-signal.md +++ b/adev/src/content/guide/signals/linked-signal.md @@ -53,6 +53,8 @@ console.log(selectedOption()); // 'Sea' shippingOptions.set(['Email', 'Will Call', 'Postal service']); console.log(selectedOption()); // 'Email' ``` +While `computed` is commonly used to derive read-only state from other signals, `linkedSignal` is helpful when the derived value should remain writable or preserve user-driven updates as its source changes. This makes `linkedSignal` a good fit for state that depends on another signal but should not be fully recomputed or overwritten on every update. + ## Accounting for previous state From da55a192e8cc0fad9f6fb3a05e1996fb0815955b Mon Sep 17 00:00:00 2001 From: Anushka Geeta Singh Date: Thu, 26 Feb 2026 22:30:12 +0530 Subject: [PATCH 3/7] docs(signals): address review feedback --- adev/src/content/guide/signals/linked-signal.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/adev/src/content/guide/signals/linked-signal.md b/adev/src/content/guide/signals/linked-signal.md index ce20cf1b1521..8d944a9c7bc3 100644 --- a/adev/src/content/guide/signals/linked-signal.md +++ b/adev/src/content/guide/signals/linked-signal.md @@ -53,9 +53,12 @@ console.log(selectedOption()); // 'Sea' shippingOptions.set(['Email', 'Will Call', 'Postal service']); console.log(selectedOption()); // 'Email' ``` + + While `computed` is commonly used to derive read-only state from other signals, `linkedSignal` is helpful when the derived value should remain writable or preserve user-driven updates as its source changes. This makes `linkedSignal` a good fit for state that depends on another signal but should not be fully recomputed or overwritten on every update. + ## Accounting for previous state In some cases, the computation for a `linkedSignal` needs to account for the previous value of the `linkedSignal`. From aecb8f4cc43de8daf69df20eb2b4ba3015042a1a Mon Sep 17 00:00:00 2001 From: Anushka Geeta Singh Date: Fri, 27 Feb 2026 18:34:20 +0530 Subject: [PATCH 4/7] docs(router): clarify command array interpretation for relative navigation --- adev/src/content/guide/routing/navigate-to-routes.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/adev/src/content/guide/routing/navigate-to-routes.md b/adev/src/content/guide/routing/navigate-to-routes.md index 99e5fa9da5f4..c0b2c4fde158 100644 --- a/adev/src/content/guide/routing/navigate-to-routes.md +++ b/adev/src/content/guide/routing/navigate-to-routes.md @@ -140,6 +140,11 @@ export class UserDetail { } ``` +⚠️ **Note on command array interpretation** + +When using `router.navigate()` with a command array and `relativeTo`, the commands are resolved as a single navigation path. Splitting relative traversal across multiple array entries (for example `['..', '..', 'child']`) may not behave as expected. Prefer combining the traversal into one segment such as `['../../child']` to ensure correct navigation. + + ### `router.navigateByUrl()` The `router.navigateByUrl()` method provides a direct way to programmatically navigate using URL path strings rather than array segments. This method is ideal when you have a full URL path and need to perform absolute navigation, especially when working with externally provided URLs or deep linking scenarios. From cd834085987d0cc2a039d24238a3d358c6e61261 Mon Sep 17 00:00:00 2001 From: Anushka Geeta Singh Date: Fri, 27 Feb 2026 18:40:26 +0530 Subject: [PATCH 5/7] revert: move router clarification to separate PR --- adev/src/content/guide/routing/navigate-to-routes.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/adev/src/content/guide/routing/navigate-to-routes.md b/adev/src/content/guide/routing/navigate-to-routes.md index c0b2c4fde158..d043c062ea93 100644 --- a/adev/src/content/guide/routing/navigate-to-routes.md +++ b/adev/src/content/guide/routing/navigate-to-routes.md @@ -139,12 +139,6 @@ export class UserDetail { } } ``` - -⚠️ **Note on command array interpretation** - -When using `router.navigate()` with a command array and `relativeTo`, the commands are resolved as a single navigation path. Splitting relative traversal across multiple array entries (for example `['..', '..', 'child']`) may not behave as expected. Prefer combining the traversal into one segment such as `['../../child']` to ensure correct navigation. - - ### `router.navigateByUrl()` The `router.navigateByUrl()` method provides a direct way to programmatically navigate using URL path strings rather than array segments. This method is ideal when you have a full URL path and need to perform absolute navigation, especially when working with externally provided URLs or deep linking scenarios. From d2d53b3c78fe00d1051939ad8fa775ad4e744dd3 Mon Sep 17 00:00:00 2001 From: Anushka Geeta Singh Date: Wed, 4 Mar 2026 21:36:44 +0530 Subject: [PATCH 6/7] ## When to prefer `linkedSignal` over `computed` While `computed` is typically used to derive read-only state from other signals, `linkedSignal` is useful when the derived state should remain writable or preserve user-driven updates as its source changes. Use `linkedSignal` when the value depends on another signal but still needs to be explicitly set or updated in response to user interaction. Additionally, `linkedSignal` should be used when you need access to the previous state while reacting to a source signal. --- adev/src/content/guide/signals/linked-signal.md | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-) diff --git a/adev/src/content/guide/signals/linked-signal.md b/adev/src/content/guide/signals/linked-signal.md index 8d944a9c7bc3..156d3ef6a920 100644 --- a/adev/src/content/guide/signals/linked-signal.md +++ b/adev/src/content/guide/signals/linked-signal.md @@ -55,10 +55,6 @@ console.log(selectedOption()); // 'Email' ``` -While `computed` is commonly used to derive read-only state from other signals, `linkedSignal` is helpful when the derived value should remain writable or preserve user-driven updates as its source changes. This makes `linkedSignal` a good fit for state that depends on another signal but should not be fully recomputed or overwritten on every update. - - - ## Accounting for previous state In some cases, the computation for a `linkedSignal` needs to account for the previous value of the `linkedSignal`. @@ -138,3 +134,15 @@ const activeUserEditCopy = linkedSignal({ equal: (a, b) => a.id === b.id, }); ``` + +## When to prefer `linkedSignal` over `computed` + +While `computed` is typically used to derive read-only state from other signals, +`linkedSignal` is useful when the derived state should remain writable or +preserve user-driven updates as its source changes. + +Use `linkedSignal` when the value depends on another signal but still needs to +be explicitly set or updated in response to user interaction. + +Additionally, `linkedSignal` should be used when you need access to the previous +state while reacting to a source signal. From ec2a1d2732b5b55bd44aa81c0970450b6b4f057b Mon Sep 17 00:00:00 2001 From: Anushka Geeta Singh Date: Fri, 13 Mar 2026 07:51:50 +0530 Subject: [PATCH 7/7] docs(docs-infra): fix mobile layout shift in API reference filters Fix layout shift in the API reference filters on mobile devices. Replaces `justify-content: space-between` with `flex-start` to prevent filter elements from redistributing space when toggled. Also adds a row gap to maintain spacing when items wrap. --- .../api-reference-list/api-reference-list.component.scss | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/adev/src/app/features/references/api-reference-list/api-reference-list.component.scss b/adev/src/app/features/references/api-reference-list/api-reference-list.component.scss index 345aeb44d8c4..f95298eb86bc 100644 --- a/adev/src/app/features/references/api-reference-list/api-reference-list.component.scss +++ b/adev/src/app/features/references/api-reference-list/api-reference-list.component.scss @@ -90,8 +90,9 @@ display: flex; gap: 1.5rem; flex-wrap: wrap; - justify-content: space-between; + justify-content: flex-start; align-items: center; + row-gap: 0.5rem; } }