Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

2
  • Looks like a good enhancement for better encapsulation. Would you agree, that Custom Form Components are not a good fit for Components, that encapsulate part of a form? Of course, if one needs to build a Library that encapsulate functionality of typically one value (e.g. a custom datepicker), then Custom Form Components would be the way to go. Commented May 2, 2018 at 10:12
  • I think having a component that encapsulates the form group as well as any form validators is a valid use case. I could see the value in having an “Address” component that has multiple fields and supports passing in an address model, that I could reuse it from multiple locations Commented May 2, 2018 at 18:21