Ant Design Form validateTrigger: Unclear validation order when using array of triggers in v5.x

Answer

Ant Design Form does not guarantee a deterministic validation order when validateTrigger is an array of trigger strings.

Confirmed facts

• The validateTrigger prop is passed to rc-field-form's Field component.
• rc-field-form creates a separate event listener for each string in the array, attaching them in the order they appear in the array.
• Validation callbacks are invoked when the corresponding DOM event fires; React may batch or reorder these events, especially in concurrent mode.

Likely explanation

The array order only influences which listener is registered first; it does not dictate the sequence in which validation runs when multiple triggers fire for the same field or across fields. Because React event handling and field mounting order can vary between renders, the observed validation order can differ.

Steps to verify

1. Create a minimal form with two fields, each validateTrigger={['onChange', 'onBlur']}.
2. Add a onFinish handler that logs form.getFieldsValue() and a validateFields callback that logs the field name and trigger.
3. Interact with the fields (type, then blur) and observe the console logs.
4. Repeat the test across different Ant Design v5.x versions (e.g., 5.0.0, 5.23.0) to see if the order changes.

How to enforce a specific validation sequence

• Use form.validateFields([fieldName], { force: true }) inside a custom event handler (e.g., onBlur) to run validation on demand.
• Wrap the field in a custom component that calls validation in the desired order.
• If you need cross‑field ordering, consider using dependencies or validateTrigger as a function that returns an array based on the current state.
• Future API could accept an object like { sequence: ['onChange', 'onBlur'] } or a validateOrder prop, but this does not exist in v5.x.

Missing diagnostic detail

If you are using React 18’s concurrent rendering mode, please confirm whether you observe non‑deterministic order; this would affect the recommendation to wrap validation in startTransition or use useSyncExternalStore for deterministic timing.