Manual validation

[timurrakhimzhan]

Can you also please add manual validation and error setting, like get.set(fieldAtoms.validate, {setErrors: true, forceVisible: true}) and setError

[lucas-barake]

What's the use case you're running into? Validation in effect-form is meant to live entirely in the schema, including async checks via refinements. Curious what scenario you're hitting that can't be expressed there.

[timurrakhimzhan]

I am persisting form values in local storage, and I want to validate fields on initial load, and only show error for non empty fields. For example I have username, which has Schema.filterEffect which validates uniqueness, user filled it with some non unique value, I persisted it, and if user refreshed page I want to still show the error "The username is already taken"

[lucas-barake]

Got it, that makes sense. I think for that case the right approach is a validateOnInit prop on Initialize that runs schema validation on mount, so persisted values get validated right away:

<form.Initialize defaultValues={savedValues} validateOnInit>
  {children}
</form.Initialize>

I'm also going to expose validate as a public atom so you can trigger it imperatively whenever you need to, not just on init:

const triggerValidate = useAtomSet(form.validate)
triggerValidate()

This keeps the schema as the single source of truth rather than allowing manual error setting. Let me know if that covers your case or if there's something it misses.

[timurrakhimzhan]

I think it would be more flexible to add validate atom for field atoms, also controlling if errors will be displayed or bot is also handy