We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
7.27.0
https://codesandbox.io/s/funny-edison-sqdvk9
After unregistering items.1.0.name, the value for items.0.0.name should still be in the watched value when watching items.
items.1.0.name
items.0.0.name
items
When I use a single-depth array this works fine (so items.0.name instead of items.0.0.name).
items.0.name
Chrome
No response
The text was updated successfully, but these errors were encountered:
This CodeSandbox uses shouldUnregister instead of unregister() with the same effect:
shouldUnregister
unregister()
https://codesandbox.io/s/charming-cherry-ptenpl?file=/src/App.tsx
Sorry, something went wrong.
fix #7849 issue with unset on multiple demision array
74779a6
🐞 fix #7849 issue with unset on multiple dimension array (#7859)
02bcbb7
* fix #7849 issue with unset on multiple demision array * remove no check
170df4a
Successfully merging a pull request may close this issue.
Version Number
7.27.0
Codesandbox/Expo snack
https://codesandbox.io/s/funny-edison-sqdvk9
Steps to reproduce
Expected behaviour
After unregistering
items.1.0.name
, the value foritems.0.0.name
should still be in the watched value when watchingitems
.When I use a single-depth array this works fine (so
items.0.name
instead ofitems.0.0.name
).What browsers are you seeing the problem on?
Chrome
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: