Link documentation to application code
Removes the "/README.md" from the links to the applications. Gitea/GitHub/etc will display the contents of the README.md file along with the code anyway, so linking this way gives better context for the application projects.master
parent
0cdd918cb4
commit
1df633dacd
|
@ -12,16 +12,16 @@ Each application implements a simple contact management form, capturing simple d
|
||||||
|
|
||||||
## Base Line - The Single component
|
## Base Line - The Single component
|
||||||
|
|
||||||
The [Base Line](apps/baseline/README.md) application implements the contact manangement form in a single angular component, directly using the example techniques from the [Reactive Forms](https://angular.io/guide/reactive-forms) documentation.
|
The [Base Line](apps/baseline) application implements the contact manangement form in a single angular component, directly using the example techniques from the [Reactive Forms](https://angular.io/guide/reactive-forms) documentation.
|
||||||
|
|
||||||
## Components Creating Own Form Controls
|
## Components Creating Own Form Controls
|
||||||
|
|
||||||
When searching the Internet for examples of nested forms in Angular, 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.
|
When searching the Internet for examples of nested forms in Angular, 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.
|
||||||
|
|
||||||
The [Parent Form](apps/parent-form/README.md) application explores this approach.
|
The [Parent Form](apps/parent-form) application explores this approach.
|
||||||
|
|
||||||
## Parent Component Creates Form and Passes Form Controls Into Child Components
|
## Parent Component Creates Form and Passes Form Controls Into Child Components
|
||||||
|
|
||||||
Another approach is to allow the outermost, or parent, component create the full Reactive Form. Each child component is given the `FormGroup` containing the portion of the form that it is responsible for rendering.
|
Another approach is to allow the outermost, or parent, component create the full Reactive Form. Each child component is given the `FormGroup` containing the portion of the form that it is responsible for rendering.
|
||||||
|
|
||||||
The [Global Form](apps/global-form/README.md) application explores this approach.
|
The [Global Form](apps/global-form) application explores this approach.
|
Loading…
Reference in New Issue