Kara

@fr0 Thanks, I was able to reproduce. We'll add this to the list!

@LanderBeeuwsaert Is there any way you could reproduce this in a Github repo instead, if Stackblitz example isn't working like your app? It's hard to investigate without a working reproduction.

@martinbu Thanks for the detailed repro! It looks like Ivy doesn't deal with `@Host` decorators well in combination with recursive components. The issue here appears to be our logic to...

Yeah, we should improve this error message. The problem is that we throw this particular one when the control does *not* have a name, so we can't provide one.

@JeanMeche It's a requirement in the design doc (pinged you in the doc so you can see it). We didn't talk about it in any great detail, but the idea...

For what it's worth, I think it makes sense to group the third-party wrappers so they are easy to find, but through a high-level guide for "third parties" and not...

As others have mentioned, the problem here is that child form directives like `formControlName` are looking to register with a parent form, and here there is no parent form above...

@gnesher Apologies for the lateness of the reply :( This is a larger issue with change detection that we are exploring how to fix with Ivy. Hopefully, we should have...

@TylerJBrown192 I don't think this has ever worked in custom value accessors, actually. The `CheckboxRequiredValidator` is a directive that specifically selects for for `input[type="checkbox"]`. With a custom value accessor, we...

@choeller Yeah, we actually wanted to build this anyway :) Unfortunately, it's a bit more complicated to build than the reactive form version because of change detection and how ngModel...