Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

why 100% components dont have any change event, not like ngModelChange #8856

Open
huymach91 opened this issue Nov 1, 2024 · 0 comments
Open

Comments

@huymach91
Copy link

huymach91 commented Nov 1, 2024

What problem does this feature solve?

because of this , it makes me hard to write reusable component which take advantage of ControlValueAccessor. As we know that this interface has 2 important methods, one is writeValue and the other is ngChange. Imagine, I have a local form group in my reuseable component, every time I update this form control in writeValue method, it triggers ngModelChange of every control of this form group. In valueChanges method, for every change, it triggers ngChange which updates formControl. Hence, it makes circular update from writeValue to ngChange and otherwise.

Can ant team implement change event rather than ngModelChange?

What does the proposed API look like?

ngModelChange

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant