jaredpalmer/formik

Validate only one field at a time

Open

#512 创建于 2018年3月13日

在 GitHub 查看
 (131 评论) (199 反应) (0 负责人)TypeScript (34,255 star) (2,801 fork)batch import
Type: Enhancementhelp wanted

描述

Bug, Feature, or Question?

Feature/Question

Current Behavior

Currently, validation is running asynchronously on the whole schema (assuming you use ValidationSchema of yup). It is reasonable to run the validation on submit, however, It is extremely cumbersome to run it on every field change/blur.

Especially if you have some backend validation (using yup.test). Assuming you have a couple of fields, field A, and field B - the later must go through backend validation. Every time you change field A, the validation runs both on A and B which will cause unnecessary backend calls.

I also tried using the new alpha version's handleChange('fieldName') but I still experience the same behavior.

Suggested Solutions

  1. Using yup schema, using yup.reach seems reasonable, even though I'm not sure how is its performance (https://github.com/jaredpalmer/formik/issues/35)

  2. Formik validate function - pass the event's field name. It will allow the developer to validate only one field at a time.

Environment

  • Formik Version: 0.11.11 /1.0.0-alpha.2
  • React Version: 16.2
  • TypeScript Version: 2.7.2
  • CodeSandbox Link:
  • OS: macOS High Sierra
  • Node Version: 8.9.4
  • Package Manager and Version:

贡献者指南

技术栈
reacttypescript
领域
frontend
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
active
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
React basicsFormik usageYup schema validation
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
40
研究方向
Investigate the current validation mechanism in Formik's source code, particularly how validation is triggered on field change and blur. Review the existing discussion in this issue for potential implementation approaches, such as using yup.reach or modifying the validate function to accept a field name. Consider performance implications and the need to maintain backward compatibility. The solution likely involves changes to the core Formik component or the useField hook.