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

Allow forced validation to run anywhere #2116

Merged
merged 1 commit into from
Dec 12, 2019
Merged

Conversation

jaredpalmer
Copy link
Owner

@jaredpalmer jaredpalmer commented Dec 12, 2019

  • Improve forced/skip validation logic in setFieldValue, setFieldTouched
  • Add second arguments to setValues, setTouched to allow for forced/skip validation

Close #2106, #2083, #1977, #2025


View rendered docs/api/formik.md

@vercel
Copy link

vercel bot commented Dec 12, 2019

This pull request is being automatically deployed with ZEIT Now (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://zeit.co/jared/formik-docs/fliwawih6
🌍 Preview: https://formik-docs-git-fix-stale-validation.jared.now.sh

@codesandbox-ci
Copy link

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 83d33a9:

Sandbox Source
Formik TypeScript Playground Configuration
Formik Codesandbox Template Issue #2106

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.

Validation runs on old value when onChange is called within onBlur
1 participant