-
-
Notifications
You must be signed in to change notification settings - Fork 266
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Redundant initial formControl valueChanges emit from quill-editor #1547
Comments
feel free to contribute and send me a pr :) |
sadly i have no solution for that. This change is triggered, because i try to keep validators in sync after the quill editor is initialized. So the control/model does have the correct valid state and classes. Seems like this triggers a change |
Maybe skip(1) to mimic angular valueChanges
|
@IsaacSomething and maybe check if the model/control is marked as touched and reset it, if needed |
I have the same problem, is there any update on this? I mean why would you emit valuechanges when nothing has changed? I have a formControl that has the default value and when I pass it to the quill editor it emits the same value... |
like described by IsaacSomething use the rxjs operator "skip" to ignore the first trigger. |
Thats not the proper way.. I have a formGroup that I track its changes and I dont always have a quill editor, or I may have more than one, so I can't just skip the first value.. Furthermore its not good for developer experience as it's not clear why this skip happens.. |
you can try to solve the issue and send a pr. but as i described above i have not idea how to solve it without breaking other functionality |
I added a hint to the readme about that issue: |
Could you provide the lines where is trigger ( so we can try help the project, starting from there) |
When using
[formControl]
to<quill-editor>
, it emit the default value throughvalueChanges
observable.This behaviour is inconsistent with the default Angular reactive form (no initial value emit but only emits when there are user changes)
Steps to reproduce
The text was updated successfully, but these errors were encountered: