Compare commits
3 Commits
e8034ac8be
...
ff1268e129
Author | SHA1 | Date |
---|---|---|
Kevin C. Coram | ff1268e129 | |
Kevin C. Coram | 5d0c467849 | |
Kevin C. Coram | f1344707e7 |
|
@ -26,7 +26,7 @@ Another approach is to allow the outermost, or parent, component create the full
|
|||
|
||||
The [Global Form](apps/global-form) application explores this approach.
|
||||
|
||||
## Parent Component Creates Form ; Child Components Define Structure
|
||||
## Parent Component Creates Form; Child Components Define Structure
|
||||
|
||||
Another approach is to allow the parent component to maintain control of creating the full Reactive Form, while allowing each child component to define the shape of the form data by means of static factory methods defined within the child component code.
|
||||
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
# Parent Component Creates Form ; Child Components Define Structure
|
||||
# Parent Component Creates Form; Child Components Define Structure
|
||||
|
||||
Another approach for refactoring a component into child sub-components where the parent component is responsible for creating the entre Reactive Form would be to define static factory methods within each child component rather than within a full-fledged service. As with the [Parent Component Creates Form and Passes Form Controls Into Child Components (Global Form)](../global-form/README.md) approach, the appropriate form controls would be passed into the children.
|
||||
|
||||
|
|
Loading…
Reference in New Issue