Skip to content
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

Handle changes to Field validate/warn props #3094

Merged
merged 1 commit into from Jun 29, 2017

Conversation

dmanningnz
Copy link
Contributor

This will ensure that changes to these functions are reflected in form
validation. Achieved by re-registing the Field with reduxForm when new
validate or warn props are recieved.

See issue: #3012

This will ensure that changes to these functions are reflected in form
validation. Achieved by re-registing the Field with reduxForm when new
validate or warn props are recieved.

See issue: redux-form#3012
@codecov-io
Copy link

codecov-io commented Jun 23, 2017

Codecov Report

Merging #3094 into master will not change coverage.
The diff coverage is 100%.

Impacted file tree graph

@@          Coverage Diff           @@
##           master   #3094   +/-   ##
======================================
  Coverage     100%    100%           
======================================
  Files          68      68           
  Lines        1449    1451    +2     
======================================
+ Hits         1449    1451    +2
Impacted Files Coverage Δ
src/createField.js 100% <100%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 994e46f...ec3667f. Read the comment docs.

@gustavohenke gustavohenke self-requested a review June 23, 2017 04:24
@erikras erikras merged commit 0b578c7 into redux-form:master Jun 29, 2017
@erikras
Copy link
Member

erikras commented Jul 11, 2017

Published in v7.0.0.

@lock
Copy link

lock bot commented Jun 1, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jun 1, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants