Add reference to blog article describing the 'own form controls' pattern
							parent
							
								
									f99b91a77e
								
							
						
					
					
						commit
						7280703c4c
					
				|  | @ -16,7 +16,7 @@ The [Base Line](apps/baseline) application implements the contact manangement fo | ||||||
| 
 | 
 | ||||||
| ## Components Creating Own Form Controls | ## 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. | The [Parent Form](apps/parent-form) application explores this approach. | ||||||
| 
 | 
 | ||||||
|  |  | ||||||
		Loading…
	
		Reference in New Issue