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

[v7.4.0] Field-level validation not working #4070

Closed
patrikmolsson opened this issue Jun 12, 2018 · 7 comments · Fixed by #4079
Closed

[v7.4.0] Field-level validation not working #4070

patrikmolsson opened this issue Jun 12, 2018 · 7 comments · Fixed by #4079

Comments

@patrikmolsson
Copy link

Are you submitting a bug report or a feature request?

Bug report

What is the current behavior?

I forked the sandbox presented here: https://redux-form.com/7.4.0/examples/fieldlevelvalidation/ and updated the redux-form version, please see https://codesandbox.io/s/vmvkqnox2y.

In the new update field-level validation functions are not triggered.

What is the expected behavior?

The validation functions are supposed to trigger.

Sandbox Link

https://codesandbox.io/s/vmvkqnox2y

What's your environment?

Chrome 65.0.3325.181,
redux-forms 7.4.0

Other information

@shamanking
Copy link

I have some issue!

@h0wXD
Copy link

h0wXD commented Jun 13, 2018

@@redux-form/CHANGE and @@redux-form/BLUR are both called but there is no @@redux-form/UPDATE_SYNC_ERRORS
In version 7.3 @@redux-form/UPDATE_SYNC_ERRORS is triggered right after @@redux-form/CHANGE

@gustavohenke
Copy link
Collaborator

Okay folks, no need to comment like this, please just react with 👍 to @patrikmolsson's opening post and it's enough for us to know how many of you have been affected.

@danielrob
Copy link
Collaborator

Please see #4069, the root cause is the same which is the lifecycle methods were updated inappropriately to their UNSAFE counterparts. Will leave this open for now for this specific symptom to be tested after the fix.

@erikras
Copy link
Member

erikras commented Jun 15, 2018

Published fix in v7.4.1.

Not fixed yet.

@erikras
Copy link
Member

erikras commented Jun 15, 2018

Published ACTUAL fix in v7.4.2.

@lock
Copy link

lock bot commented Jun 15, 2019

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 15, 2019
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 a pull request may close this issue.

6 participants