fix(ref: 1560): added handling of "writingValue" variable to avoid th… #1570
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.
…e propagation of the changed value
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: 1560
The input / form is marked as dirty on initial load.
What is the new behavior?
The input / form is not marked as dirty on initial load.
Does this PR introduce a breaking change?
Other information
The initial load of the form changes the input value, but tries to avoid the propagation of the event to the angular model by setting "writingValue" to true. The comment on the function says "It won't do this if writingValue is true", but there was no handling of the variable in the code, except it was set to "false" every time.