Maxime

Just another thought on that: If we turn `emitEvent` to `true`, with https://github.com/cloudnc/ngx-sub-form/issues/103 we'd broadcast up an empty object which is likely to be an error. Also, if the RootForm...

Discussed offline with @zakhenry and Ty: - We should follow what angular does by default: emit the value when the form is enabled/disabled - It's easy to not trigger downstreams...

:tada: This issue has been resolved in version 5.2.0-feat-rewrite.1 :tada: The release is available on: - [npm package (@feat-rewrite dist-tag)](https://www.npmjs.com/package/ngx-sub-form/v/5.2.0-feat-rewrite.1) - [GitHub release](https://github.com/cloudnc/ngx-sub-form/releases/tag/v5.2.0-feat-rewrite.1) Your **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package::rocket:

Hi @ntziolis, could you please create a small repro on Stackblitz https://stackblitz.com/fork/angular so we can understand if there's already an easy way of doing it and otherwise it'll be useful...

@ntziolis I'm not saying this will happen but I'm considering the option. I think we could have for ex `NgxSubFormSingleValueComponent` (please propose a better name if you can think of...

I did give a go at this... And here's the best I could achieve: ```ts type Impossible = { [P in K]: never; }; export type NoExtraProperties = U extends...

:point_up: the above didn't work it always had edge cases not working, there's a typescript issue that we can track though which might make this doable at compile time: https://github.com/microsoft/TypeScript/issues/12936

Test LGTM :+1: nice one

Could you please create an issue to explain what you've found out and link this MR to it? Will be easier to keep track of it

Also to clarify, as it's just typing the current work around is just to apply `as any` on all the `null` values but this is obviously not ideal.