ngModel complains when used with @defer about angular HOT 5 CLOSED

I already updated my code to use ngModelOptions, however, I tried this version on the failing stackblitz and I can reproduce the issue so I guess it is correctly fixed :-)

Thanks for the quick action.

from angular.

@ssougnez thanks for reporting the issue and providing a repro. The issue might be related to #54864 and we are working on a fix. While working on a fix for #54864, we can put together a test that would check Forms behavior as well. Will keep this thread updated once we make more progress.

from angular.

Quick update: I've confirmed that the root cause of this issue is the same as the one from #54864. We are working on a fix and will keep this thread updated once the fix is available.

And just out of curiosity, is it a bad practice to have a component using ngModel for just one two-way binding without using ngModelOptions?

If you do not rely on that <input> to act as a part of a larger form (and only used to sync a value between an input and a class field), you may consider using the ngModelOptions.standalone flag.

It never occurred to me so I was not doing it but now that I'm facing this issue, I'm wondering whether I should start using ngModelOptions in these cases.

The issue was caused by the bug in Angular's code, adding @defer should not cause the error in your scenario.

from angular.

Okay thanks.

And just out of curiosity, is it a bad practice to have a component using ngModel for just one two-way binding without using ngModelOptions?

It never occurred to me so I was not doing it but now that I'm facing this issue, I'm wondering whether I should start using ngModelOptions in these cases.

from angular.

Quick update: the fix for this issue was merged and released as a part of Angular v17.3.2 (available on NPM). Please let us know if you still see the issue after updating to v17.3.2.

from angular.