From f1344707e777ca19973b92860d0f658824d821d2 Mon Sep 17 00:00:00 2001 From: "Kevin C. Coram" Date: Wed, 8 Jan 2020 22:05:08 -0500 Subject: [PATCH] Stronger statement about potential problem with tying form creation to component rendering --- apps/parent-form/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/parent-form/README.md b/apps/parent-form/README.md index eec92b7..0963432 100644 --- a/apps/parent-form/README.md +++ b/apps/parent-form/README.md @@ -78,6 +78,6 @@ Calling `this.parent.addControl(....)` is what ensures that the controls created ## Cons -- The creation of the form controls is tightly coupled with the templates +- The creation of the form controls is tightly coupled with the templates, to the point that if a child component is not rendered for some reason, the form controls won't exist either. - Since each child component encapsulates its form controls, the overall shape of the form data is not always clear