Skip to content
TheChatArchiveThe Chat Archive
x-ai/grok-4.5· unknownHugging Face ibragim-bad/swe_rebench_07_2026_trajectories

ISSUE DESCRIPTION issue: values data is reset after first render, when shouldUnregister…

  1. User

    ISSUE DESCRIPTION

    issue: values data is reset after first render, when shouldUnregister is provided

    Version Number

    7.71.2

    Codesandbox/Expo snack

    https://codesandbox.io/p/sandbox/blazing-dust-3225h9?file=%2Fsrc%2FApp.js

    Steps to reproduce

    1. Simply submit a form
    2. See error

    Expected behaviour

    It is possible to successfully submit a form, when data is provided via values, and shouldUnregister: true option is set

    What browsers are you seeing the problem on?

    Chrome

    Code of Conduct

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

    Interface

    No new interfaces are introduced.

    ADDITIONAL ADVICE

    Since you are given a git repository, you can use git commands to simplify your work. For example, if you made a mistake and want to revert your changes, you can use git checkout <file> to restore the file to its original state. You can also reset all changes in the repository using git reset --hard command. Additionally, you can use git stash and git stash pop to temporarily save your changes and restore them later. Finally, you can see the changes that you've made (which will be submitted when you call submit) using git status or git diff commands. However you don't need to use git add or git commit before submitting your changes. In fact, submit only submits currently unstaged changes because it uses git diff to get the changes that need to be submitted.

    CHECKLIST

    Before submitting your solution, please go over the following checklist and make sure you've done everything:

    • If an error was reported in the issue description, I have successfully reproduced it.
    • If an error was reported in the issue description, I have confirmed that my fix resolves the error.
    • I have thought about edge cases and made sure my fix handles them as well.
    • I have run existing tests in the repository that might have been affected by the change I made and confirmed that they pass. I want you to list every bullet from this checklist and write your reasoning for why you think you did it or didn't need to.

    Repository has been uploaded and your shell is currently at the repository root. Time to solve the issue!

    (Current directory: /react-hook-form, current file: none) bash-$

  2. Assistant

    I'll start by exploring the repository structure and reproducing the issue described.

  3. Assistant

    Let me examine the source code related to values and shouldUnregister.

  4. Assistant

    Let me look at the issue more carefully. The codesandbox is about values being reset when shouldUnregister is true. Let me search for related tests and code.

  5. Assistant

    rg not found, use grep instead.

  6. Assistant

    Let me look at how values interacts with shouldUnregister in the form control and related tests.

  7. Assistant

    Let me read the useForm and createFormControl related to values.

  8. Assistant

    Let me examine useForm.ts and the values/reset flow more carefully.

  9. Assistant

    Let me read the rest of useForm.ts

  10. Assistant

    Let me examine createFormControl's initialization and reset handling for shouldUnregister.

  11. Assistant

    Let me examine the reset function and related tests for values with shouldUnregister.

  12. Assistant

    I found a suspicious piece of code. Let me continue reading the reset function and check related tests/history.

  13. Assistant

    Let me check how keepFieldsRef interacts with mount names and search for related issues/fixes.

  14. Assistant

    Let me look at tests related to the values prop and how handleSubmit gathers form data.

  15. Assistant

    Let me try to write a minimal reproduction based on the issue description.

  16. Assistant

    Let me look at the values-related tests around line 2255 in useForm.test.tsx

  17. Assistant

    Let me write a temporary reproduction script to confirm the bug.

  18. Assistant

    Need to fix the import path.

  19. Assistant

    Confirmed the bug. Let me dig into register and handleSubmit to find the right fix.

  20. Assistant

    Let me inspect _getWatch and how submit collects values.

  21. Assistant

    Let me look at handleSubmit more carefully.

  22. Assistant

    Let me check when this shouldUnregister logic in reset was introduced and look at related PR history.

  23. Assistant

    Let me look at the CHANGELOG and any related GitHub issues or recent similar bugs.

  24. Assistant

    There's a recent related fix. Let me inspect it.

  25. Assistant

    That was a useController fix. Let me look at it.

  26. Assistant

    Let me check the types for keepFieldsRef and existing reset tests.

  27. Assistant

    I'll implement the fix in _reset to preserve form values and mount names when keepFieldsRef is set.

  28. Assistant

    Let me apply the fix.

  29. Assistant

    Let me run the reproduction test to verify the fix.

  30. Assistant

    The fix works. Let me expand tests for edge cases and run existing related tests.

  31. Assistant

    All edge cases pass. Now I'll run the related existing tests.

  32. Assistant

    Related tests passed. Running more shouldUnregister-related tests.

  33. Assistant

    All tests passed. Cleaning up the temporary test and reviewing the final diff.

  34. Assistant

    I'll simplify the comment to match the codebase style.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.