issue: Two useFieldArray instances are not able to modify the same array

[bolencki13]

Version Number

7.51.5

Codesandbox/Expo snack

https://codesandbox.io/p/sandbox/divine-shape-4s2zy9

Steps to reproduce

1. Go to code sandbox link
2. Click on "Remove 0 (same useFieldArray WORKS)". Observe the 0th element in the list be removed
3. Click on "Remove 0(separate useFieldArray DOES NOT WORK)". Observer nothing is removed from the list

Expected behaviour

I would expect any instance of useFieldArray referencing the same list to be able to modify said list.

What browsers are you seeing the problem on?

Chrome

Relevant log output

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[BrendanC23]

The docs say this about using multiple field arrays:

Each useFieldArray is unique and has its own state update, which means you should not have multiple useFieldArray with the same name.

I think this is working as intended. Can you just pass the fieldArray to <JobActions />?

[bolencki13]

This seems like a bit of a design flaw. One of the benefits of a context is to prevent passing props down the chain. While in the minimal example above it might make sense to pass this instance around, in a more complex real world example it seems like an anti-pattern having to create an instance top level and pass it down multiple branches various levels.

I'd like to understand the design choice, is there a particular reason for this requirement?