Tim Kindberg

I definitely do not follow completely. I think you are saying this is a pattern that could be followed to "try the api out"? Wouldn't someone just add the `whenCalledWith`...

may be good to pass `formState` as well while you are at it. I have a use case where I have a nested react-json-schema-form that I want to validate but...

> doesn't work with resolver, its only for build-in validation, also formState is trigger such as touched field state and dirty, state update is on the next render I don't...

> That's a good use case to use trigger as you control when to fire the validation. hmm ok but can you control when to NOT fire? Validate function seems...

> The frequency of the validate callback running corresponds to the mode passed to useForm: that’s not what I’ve experienced. We have it set to onSubmit but I see that...

I'm having this issue as well. For some reason it's also printing out a bunch of JS. It's happening after upgrading to v6.2.9 to try and get Webpack 5 working....

I also got a TON of `"loose"` messages... tried to shut them up but no success.

That's odd because I `rm -rf node_modules` multiple times and `npm i` fresh. And I was still having the issue. So not sure how deleting the cache would have fixed...

Seeing this as well after updating to 12.2.5. Operating System: Platform: darwin Arch: x64 Version: Darwin Kernel Version 21.2.0: Sun Nov 28 20:28:41 PST 2021; root:xnu-8019.61.5~1/RELEASE_ARM64_T6000 Binaries: Node: 14.18.3 npm:...

@ijjk canary.1 seemed to solve it for me but I rolled back to 12.2.4 instead.