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 Feb 16, 2021. It is now read-only.
In Struct and List components, t.validate is called with value that is built by their child components (i.e. with values that are results of calling child components validate method).
In getTypeInfo (util module), or more precise in getValidationErrorMessage method that is built, t.validate is called with value that is received from base Component's getError method. That value is built from state with calling top level transformer only.
One of the consequences is that if struct or list item type has properties of types that are parsed by their own transformers (e.g. number type), and valid strings are set for those properties, case 1. will not find validation errors (since those strings are parsed by their components, when their validate method is called), but case 2. will find validation errors (since those strings are not parsed)
The text was updated successfully, but these errors were encountered:
One of the consequences is that if struct or list item type has properties of types that are parsed by their own transformers (e.g. number type), and valid strings are set for those properties, case 1. will not find validation errors (since those strings are parsed by their components, when their validate method is called), but case 2. will find validation errors (since those strings are not parsed)
The text was updated successfully, but these errors were encountered: