Form.Item noStyle + shouldUpdate Interoperability with Parent Form Validation

Answer to the core questions

1. Does a noStyle Form.Item with shouldUpdate automatically update the parent Form’s validation state in Ant Design v5?

No. In v5 the validation status of a noStyle child no longer bubbles up to ancestor Form.Items unless the ancestor explicitly declares a dependency on the child’s field or itself uses shouldUpdate with a dependencies array.

2. What internal change caused the parent to miss child validation updates?

v5 refactors the Form context so that noStyle items are isolated from the parent’s validation tree. The implicit propagation path that existed in v4 was removed; the parent now only reacts to changes that trigger its own shouldUpdate logic.

3. Is there a documented pattern that guarantees propagation in v5?

Yes. Wrap the noStyle child inside a parent Form.Item that has shouldUpdate set to true and lists the child’s field names in its dependencies array. This forces the parent to re‑evaluate whenever the child’s value or validation status changes, merging the child’s errors into the parent’s error list.

Practical steps for v5

1. Define the child field with noStyle and any validation rules.
2. Wrap the child in a parent Form.Item like so:

{/* Parent wrapper */}
 
   
     
  

When the user interacts with the child (e.g., on blur), the parent’s shouldUpdate logic triggers and the error styling appears immediately.

Optionally, you can call form.validateFields(['childField']) in the child’s onChange handler to force validation without the dependencies array, but this adds extra API calls.

Verification checklist

• Render the form in a browser and trigger validation by typing and blurring the child field.
• Open the console and run form.getFieldError('childField') – the error should appear.
• Run form.getFieldError('parentField') if you have a parent field; the child’s error should now be merged into the parent’s error list.
• Remove the dependencies array and observe that the parent no longer updates automatically.

Ask for missing detail

To confirm whether the parent Form.Item has a dependencies array, could you share that part of the code? This will help ensure the recommendation applies to your exact setup.