Skip to content

fix(ref: 1560): added handling of "writingValue" variable to avoid th… #1570

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

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

grospolina
Copy link

…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?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • Other... Please describe:

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?

  • Yes
  • No

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.

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

Successfully merging this pull request may close these issues.

1 participant