Fix multiple subscriptions to same observables on form activation #299
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixed an issue where some observables were subscribed multiple times each time the activateForm method is called.
The
activateForm
method is called insetValues
method which is called when the form config is updated causing emitters (onChanges
,changeDetector
,isValid
,validationErrors
) to emit at least twice after first form init and the number of emits increases each time the form config is updated.When config is changed all emitters emit for each input present in the layout, as it was not unsubscribed a new subscription
is created on each iteration...