fix(core): change form validity when expressionProperty change. #590
Conversation
This file contains 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
Codecov Report
@@ Coverage Diff @@
## master #590 +/- ##
==========================================
+ Coverage 92.93% 94.09% +1.15%
==========================================
Files 16 16
Lines 736 745 +9
Branches 212 215 +3
==========================================
+ Hits 684 701 +17
+ Misses 52 44 -8
Continue to review full report at Codecov.
|
aitboudad
pushed a commit
that referenced
this pull request
Dec 8, 2017
…ionProperty change. (#590) fix #582 Triggered by commit: 290761c Travis build: https://travis-ci.org/formly-js/ngx-formly/builds/313577385
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What kind of change does this PR introduce? Bug fix
fix #582
This change is