Skip to content

issue: Calling reset triggers subscribe with latest name instead of undefined #13569

Description

@BrendanC23

Version Number

7.80

Codesandbox/Expo snack

https://codesandbox.io/p/devbox/zealous-brook-4nqqqz

Steps to reproduce

  1. Click on the reset button. undefined is printed
  2. Type a into the firstName field. firstName is printed
  3. Click the reset button again. Now, firstName is printed

Expected behaviour

When a subscription callback is triggered from a reset call, the name should be undefined, not the value of the last field that was edited with setValue

What browsers are you seeing the problem on?

Chrome

Relevant log output

Code of Conduct

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions