From 7280703c4c4374098c81b214c049a6e81c9de8ac Mon Sep 17 00:00:00 2001 From: "Kevin C. Coram" Date: Tue, 31 Dec 2019 13:06:42 -0800 Subject: [PATCH] Add reference to blog article describing the 'own form controls' pattern --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 67df31e..b6fa7eb 100644 --- a/README.md +++ b/README.md @@ -16,7 +16,7 @@ The [Base Line](apps/baseline) application implements the contact manangement fo ## Components Creating Own Form Controls -Searching the Internet for examples of nested forms in Angular shows one popular approach is to have each sub-component be responsible for creating its own form controls. The parent form is passed in as an `@Input`, and the component adds its components to the form using the `addControl(name, control)` method. +Searching the Internet for examples of nested forms in Angular shows one popular approach is to have each sub-component be responsible for creating its own form controls. The parent form is passed in as an `@Input`, and the component adds its components to the form using the `addControl(name, control)` method. See, for example, [Nested Reactive Forms in Angular2](https://www.brophy.org/post/nested-reactive-forms-in-angular2/). The [Parent Form](apps/parent-form) application explores this approach.