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
Currently, zSchema will only report required errors for the top-level field missing. ember-frost-bunsen relies on these messages to highlight fields that are missing. There was previous work done before to resolve this by making all required fields initialized with empty objects but that was a contradiction to the meaning of required as it allowed the form to pass validation without errors for required fields.
What needs to be done is to replace the required errors with errors targeting the child fields. This can be tricky with arrays because arrays can't be further processed without having a value. Unlike an object whose fields are statically defined, the length of an array is dynamic.
What complicates this further is a form can reference an array item without having the array item exist initially but we need to provide appropriate error messages for them as well. So we would obviously need to tap into the view schema during this processing.
The text was updated successfully, but these errors were encountered:
Currently, zSchema will only report required errors for the top-level field missing.
ember-frost-bunsen
relies on these messages to highlight fields that are missing. There was previous work done before to resolve this by making all required fields initialized with empty objects but that was a contradiction to the meaning of required as it allowed the form to pass validation without errors for required fields.What needs to be done is to replace the
required
errors with errors targeting the child fields. This can be tricky with arrays because arrays can't be further processed without having a value. Unlike an object whose fields are statically defined, the length of an array is dynamic.What complicates this further is a form can reference an array item without having the array item exist initially but we need to provide appropriate error messages for them as well. So we would obviously need to tap into the view schema during this processing.
The text was updated successfully, but these errors were encountered: