space10-community/conversational-form

Improve validation for native HTML5 input field types

Open

#228 opened on Mar 24, 2018

View on GitHub
 (3 comments) (0 reactions) (0 assignees)HTML (3,772 stars) (789 forks)batch import
enhancementhelp wanted

Description

Hey team! Just wanted to say how awesome this project is. I do believe this to be the future of forms. I would like to recommend a feature request for more simple native validation.

  • description of the actual behavior Validation is unnecessarily complex. I have not only recently successfully validated an <input name='' type='email'> with flowStepCallback.

More examples in the docs for each input type would get the community a lot further. Research shows that users agree that "handling validation for some questions is unnecessarily complex". Even simple min/max validation is left unanswered.

  • expected behavior When a native input field errors the cf-error="This field is invalid yo" message should automatically interrupt the form flow and display its message to the user by default. Use of flowStepCallback and regex patterns should be overrides for custom validation purposes.

This way conversational forms can be used out the box for everyone leaving custom validation work to advanced users.

Contributor guide

Tech stack
htmlcssjavascript
Domain
frontend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Familiarity with conversational form libraryUnderstanding of HTML5 input validation
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
The issue requests that native HTML5 validation errors automatically interrupt the form flow and display the cf error message. Research the current validation handling in the library, particularly the flowStepCallback and how cf error is implemented. Look at the linked issue #56 for context. Investigate the codebase to understand how validation is triggered and where to intercept native validation errors. Consider proposing a change that allows native validation to take precedence unless overridden by custom validation.