Ali Emir Şen

Just checked out the codebase you've provided @khoaxuantu. I was able to reproduce the same rendering issue with the initial setup. Then it resolved when I removed the `onClick` prop...

Hey @khoaxuantu you are right! My bad, I only tested out in the same page and hot reloading fixed the issue when I made changes in the `` 🤦 I...

Hey @Anonymous961 yeah this is what I tried, would love to hear from you if you can spare some time to work on this 🙏

Thanks to @benmccann, this issue is addressed in #6250 for `@refinedev/devtools-server`. `preferred-pm` is also used in `@refinedev/cli` and same changes can be applied to it as well. If anyone is...

Hey @noritsune thank you for the issue! I think I understand the problem here. While the `useForm` hook from `@refinedev/core` exposes an `onFinish` handler to submit values and doesn't integrate...

@chhaysotheara thank you for bumping the issue 😅 I'm leaving this comment as an implementation guide that we can follow when working on this feature. Using a union type for...

Hey @mjbergman92, I think I understand the issue here. `` may register the field after the first run and our effect may miss it when we're setting the values. We...

Hey @arndom, I've tried on my local but looks like the effect is exceeding the max depth and even if I ignore it, it starts looping when I have a...

Hey @pcfreak30 👋, I've checked the code you've provided and investigated the issue for a bit. Looks like calling `setValue` doesn't add `type` to the subscription calls but registered controls/fields...

Sorry for the late response. Instead of having `setValue` to update the form values according to the inputs, you should use the `onChange` from the `register("my-field")`'s return values or `onChange`...