This repository was archived by the owner on Sep 8, 2020. It is now read-only.
Do not set the parent form to pristine on init#259
Open
pelizza wants to merge 1 commit intoangular-ui:masterfrom
Open
Do not set the parent form to pristine on init#259pelizza wants to merge 1 commit intoangular-ui:masterfrom
pelizza wants to merge 1 commit intoangular-ui:masterfrom
Conversation
…control the form state.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
The field should not control form state.
The issue was found when enabling ui-tinymce directive inside a form, which had other fields. When it enables, all other fields are set to pristine, since ui-tinymce set the form to pristine.
This behaviour has been removed.