From d5fcde870d97a15dfe452d73234eaece533d5086 Mon Sep 17 00:00:00 2001
From: ZainnQureshii <43629888+ZainnQureshii@users.noreply.github.com>
Date: Thu, 24 Sep 2026 16:31:15 +0200
Subject: [PATCH 1/2] docs(angular): fix source paths in component guide

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
---
 docs/component-guide.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/component-guide.md b/docs/component-guide.md
index f685fd6163d..33534d49fe2 100644
--- a/docs/component-guide.md
+++ b/docs/component-guide.md
@@ -835,14 +835,14 @@ When creating a new component that renders native input elements (such as `<inpu
 
 For Angular integration, you should use one of the existing value accessors based on your component's needs. Choose the one that most closely matches your component's behavior:
 
-- For text input (handles string values): Use [`TextValueAccessorDirective`](/packages/angular/src/directives/control-value-accessors/text-value-accessor.ts) which handles `ion-input:not([type=number])`, `ion-input-otp[type=text]`, `ion-textarea`, and `ion-searchbar`
-- For numeric input (converts string to number): Use [`NumericValueAccessorDirective`](/packages/angular/src/directives/control-value-accessors/numeric-value-accessor.ts) which handles `ion-input[type=number]`, `ion-input-otp:not([type=text])`, and `ion-range`
-- For boolean input (handles true/false): Use [`BooleanValueAccessorDirective`](/packages/angular/src/directives/control-value-accessors/boolean-value-accessor.ts) which handles `ion-checkbox` and `ion-toggle`
-- For select-like input (handles option selection): Use [`SelectValueAccessorDirective`](/packages/angular/src/directives/control-value-accessors/select-value-accessor.ts) which handles `ion-select`, `ion-radio-group`, `ion-segment`, and `ion-datetime`
+- For text input (handles string values): Use [`TextValueAccessorDirective`](/packages/angular/src/lazy/directives/control-value-accessors/text-value-accessor.ts) which handles `ion-input:not([type=number])`, `ion-input-otp[type=text]`, `ion-textarea`, and `ion-searchbar`
+- For numeric input (converts string to number): Use [`NumericValueAccessorDirective`](/packages/angular/src/lazy/directives/control-value-accessors/numeric-value-accessor.ts) which handles `ion-input[type=number]`, `ion-input-otp:not([type=text])`, and `ion-range`
+- For boolean input (handles true/false): Use [`BooleanValueAccessorDirective`](/packages/angular/src/lazy/directives/control-value-accessors/boolean-value-accessor.ts) which handles `ion-checkbox` and `ion-toggle`
+- For select-like input (handles option selection): Use [`SelectValueAccessorDirective`](/packages/angular/src/lazy/directives/control-value-accessors/select-value-accessor.ts) which handles `ion-select`, `ion-radio-group`, `ion-segment`, and `ion-datetime`
 
 These value accessors are already set up in the `@ionic/angular` package and handle all the necessary form integration. You don't need to create a new value accessor unless your component has unique requirements that aren't covered by these existing ones.
 
-For example, if your component renders a text input, it should be included in the `TextValueAccessorDirective` selector in [`text-value-accessor.ts`](/packages/angular/src/directives/control-value-accessors/text-value-accessor.ts):
+For example, if your component renders a text input, it should be included in the `TextValueAccessorDirective` selector in [`text-value-accessor.ts`](/packages/angular/src/lazy/directives/control-value-accessors/text-value-accessor.ts):
 
 ```diff
 @Directive({
@@ -1004,7 +1004,7 @@ These files contain tests for input behavior. Review how similar components are
 
 Add your component's interfaces to the framework packages:
 
-1. Angular ([`packages/angular/src/index.ts`](/packages/angular/src/index.ts)):
+1. Angular ([`packages/angular/src/lazy/index.ts`](/packages/angular/src/lazy/index.ts) and [`packages/angular/src/standalone/index.ts`](/packages/angular/src/standalone/index.ts)):
 ```typescript
 export {
   NewComponentCustomEvent,

From 38b4c609be6503dd453e0db6a8785b5f17d988cc Mon Sep 17 00:00:00 2001
From: ZainnQureshii <43629888+ZainnQureshii@users.noreply.github.com>
Date: Thu, 24 Sep 2026 19:48:50 +0200
Subject: [PATCH 2/2] docs(angular): note standalone exports interfaces from
 @ionic/core/components

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
---
 docs/component-guide.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/component-guide.md b/docs/component-guide.md
index 33534d49fe2..83698480020 100644
--- a/docs/component-guide.md
+++ b/docs/component-guide.md
@@ -1004,7 +1004,7 @@ These files contain tests for input behavior. Review how similar components are
 
 Add your component's interfaces to the framework packages:
 
-1. Angular ([`packages/angular/src/lazy/index.ts`](/packages/angular/src/lazy/index.ts) and [`packages/angular/src/standalone/index.ts`](/packages/angular/src/standalone/index.ts)):
+1. Angular ([`packages/angular/src/lazy/index.ts`](/packages/angular/src/lazy/index.ts) and [`packages/angular/src/standalone/index.ts`](/packages/angular/src/standalone/index.ts), which exports these from `@ionic/core/components` instead):
 ```typescript
 export {
   NewComponentCustomEvent,