issue: With a `<DevTool />`, `watch` is not triggered by `setValue`

Open
#196 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
react, typescript
Domain
devtools, frontend

Research direction

Start with the linked CodeSandbox, especially src/index.tsx, and reproduce the behavior with and without the component. Trace how setValue and watch behave in each case; done means watch is triggered consistently in both configurations, with the reproduction still passing in Chrome.

Written by the indexing model from the issue text.

Description

Version Number

react-hook-form: 7.43.5; react: 18.2.0

Codesandbox/Expo snack

https://codesandbox.io/s/hookform-devtools-bug-watch-is-not-triggered-by-setvalue-mhcjlx?file=/src/index.tsx

Steps to reproduce

https://user-images.githubusercontent.com/38932402/225195576-d5ae222f-4474-4de8-81be-8013c66ff1e3.mp4

Expected behaviour

setValue should correctly trigger watch whether there's a <Devtool /> or not.

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
Dominant language
TypeScript
Stars
670
Forks
55
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from react-hook-form/devtools

All issues in react-hook-form/devtools

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.