liveValidate should optionally not validate "pristine" fields (at least until a submit) · rjsf-team/react-jsonschema-form#512

(31 评论) (24 反应) (0 负责人)TypeScript (13,175 star) (2,136 fork)batch import

featurehelp wanted

描述

Prerequisites

I have read the documentation;
In the case of a bug report, I understand that providing a SSCCE example is tremendously useful to the maintainers.

Description

In the playground, the "Validation" tab, when live validation is enabled, starts with an error ("passwords don't match"). However, the user hasn't put in a password yet, so it doesn't make sense as part of the user experience to show this error, at least until they start typing in the field.

Similarly, in the "Errors" tab, the initial state shows a bunch of errors. However, for some user experiences, this doesn't seem necessary or helpful; we're telling the user about errors that pre-existed, not errors they themselves have made.

Per https://github.com/mozilla-services/react-jsonschema-form/issues/246#issuecomment-286277405, maybe we should not validate fields until they've been "touched" somehow.

贡献者指南

技术栈: reacttypescript
领域: frontend
议题类型: feature
难度: 3
预计时间: half day
活动状态: stale
清晰度: clear
前置要求: ReactJSON Schemaform validation
新手友好度: 70
研究方向: Explore the current implementation of live validation in the Form component (likely in src/Form.js). Understand how the liveValidate prop triggers validation on every change. Then, add a new prop to skip validation on pristine fields. Refer to the discussion in issue #246 and the linked comment for context. Consider implementing a simple flag that defers validation until the field is touched or form is submitted.