useFieldArray reactivity when removing fields

[jhrr]

I'm having an issue with useFieldArray reactivity. I'm unsure if it's actually a bug or if I've just made a mistake/overlooked something, so I thought I'd raise it here rather than make a full issue out of it immediately.

I've made a codesandbox isolating the core issue I'm experiencing, and it's consistently reproducible in both my own project and in the sandbox.

You can see that here:

https://codesandbox.io/s/frosty-kilby-uk5lus

If you add several select fields and set them to random values you will see the fields data update correctly and render out in the JSON blob. The values data returned by useForm also updates correctly. So far, so good.

Then, if you start removing the fields one by one you can see that while the data does update as expected internally, the select fields do not render correctly when the UI is updated.

Note, I do have the additional toRef(props, "name") on the useField invocation in the select field sub-component, as described in the docs.

Like I say, maybe I am just overlooking some detail, missing some reactive declaration somewhere maybe? But if I am I can't see what it is! So, I would appreciate another set of eyes and a sanity check on this.

Cheers, and thanks for all the effort on the library, it's much appreciated.

[jhrr]

Promoted this to an issue after several days of banging my head against the wall. There are further problems I'm having with useFieldArray and validation but I think they might just be a side-effect of whatever is going on here.

[logaretm]

Seems to work fine if I use the data name for the fields instead of fields. In the useFieldArray you are declaring data as the iterable while having fields as the iterable in the template so they won't be synced when doing array mutations.

https://codesandbox.io/s/jolly-nobel-edfr5m

Can you confirm if that's the issue or not?

[jhrr]

Ahh thanks @logaretm that does indeed looks like it resolve it! As I thought needed another pair of eyes on it.

I'll close the issue I opened on the back of this.

Many thanks.

[logaretm]

No worries, sorry for the delay. I should've answered this earlier and creating the issue did notify me of this one. Glad it works for you now.