You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 23, 2022. It is now read-only.
We use this package for a lot of forms, managed it very well, but still stacked with this issue: when we try to enable / disable "submit" button according to form validation state- $form.valid is false although no client errors appear, only server error (that we added via "asyncSetValidation").
is there any way to make a difference between "client valid" and "server valid"?
Steps to Reproduce
Create a form using RRF
Use simple Field component, and use client validation like "required".
add onSubmit validation and use asyncSetValidation to raise server validation error.
Fill in this field so required will not raise client error.
The Problem
We use this package for a lot of forms, managed it very well, but still stacked with this issue: when we try to enable / disable "submit" button according to form validation state- $form.valid is false although no client errors appear, only server error (that we added via "asyncSetValidation").
is there any way to make a difference between "client valid" and "server valid"?
Steps to Reproduce
Expected Behavior
$form.valid is true
Actual Behavior
$form.valid is false
Reproducible Code Example
(please fork from this CodePen template or this CodeSandbox template)
The text was updated successfully, but these errors were encountered: