KimJunYoung

The behavior of `reset` has been changed since a loop was added to call setValue for each field. This change was introduced in one of the PRs in `7.55.0-next.8`, specifically...

@Jarzka Thanks for sharing your opinion! I was really confused when I investigated this issue. 😁 @bluebill1049 As always, I’m amazed at how quickly you respond, Bill. Truly respect your...

@buondevid I’m curious what you think about using the [reset](https://react-hook-form.com/docs/useform/reset) method. While detecting changes to the initial value stored in state and reacting on them would keep the consumer’s code...

@kysemon I think that you'd better describe your environment. It works well in my project. Here is my `package.json` ```json { "name": "react-hook-form-pr-test", "version": "0.1.0", "private": true, "scripts": { "dev":...

@FezVrasta Hello! @FezVrasta Could you please check the [[The readonly attribute specification]](https://html.spec.whatwg.org/)? You can find a note explaining the difference between `readonly` and `disabled`.

@FezVrasta Oh, I misunderstood earlier. It definitely seems odd for validation to be applied when the input is `read-only`.

@AnzeKop In #1907, the following phrase appears: > setError error will be removed by validation rules, rules always take over errors. To me, this explanation means that errors set with...

@AnzeKop > the docs desdube that setError is what should be used in the submit function for custom validation and for blocking submission Could you share any documentation that states...

@AshotN > if anything is in form.formState.errors then form.formState.isValid would be false I agree with your opinion. At the very least, some users would naturally think that if errors exist...

@bluebill1049 Hi Bill, I think having the rules/resolver as the source of truth is a core philosophy of `RHF`, and many people have already become accustomed to this behavior, so...