Overview - Form

form

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
2133
a1294aad fix(form-core): properly scope avoidTouch to removeFieldValue only The previous fix bypassed validateField for all calls to validateArrayFieldsStartingFrom, which broke: - validateArrayFieldsStartingFrom when called directly (expected isTouched) - replaceFieldValue (expected errors to appear on validation) - removeFieldValue (expected errors to appear on validation) The fix now uses an avoidTouch option that: 1. Only prevents permanently marking fields as touched during removeFieldValue 2. Temporarily sets isTouched=true to allow validation to run (so errors are still collected), then restores the original isTouched state 3. All other callers use the default behavior (validateField with touch)
by Maks Pikov
Failed
2133
cd491bac fix(form-core): prevent removeValue from auto-touching shifted siblings When calling form.removeValue(index) on an array field, isTouched was incorrectly set to true on every sibling at index >= removed index, even when the user never interacted with those fields. The fix bypasses validateField for fields with existing instances and calls fieldInstance.validate() directly, which preserves validation without the auto-touch side-effect. Fixes #2131
by Maks Pikov