i tried to find the issue for about 2 days but could recreate it and the app is working fine maybe i could't recreated the issue here is the proof
video link

Hey @Varun789-mx , you are showing the bug in the video. You removed a space and added it back, so there are no changes, but the warning is popping up saying you have unsaved changes.

Hello @jpenna, thanks for the issue.

I think we can check React Hook Form's isDirty state and use it to handle warnWhenUnsavedChanges.

Hello @alicanerdurmaz, Can i work on this?

Yes @mohit-2003, thanks for improving Refine 🙌

Hello @jpenna, thanks for the issue.

I think we can check React Hook Form's isDirty state and use it to handle warnWhenUnsavedChanges.

Hi @alicanerdurmaz, I tested isDirty, but it doesn't work as expected. The issue is that isDirty remains true even after reverting changes back to the original values. I think we have to compare old values and new values for this, do you any other idea?

Hello @jpenna, thanks for the issue.
I think we can check React Hook Form's isDirty state and use it to handle warnWhenUnsavedChanges.

Hi @alicanerdurmaz, I tested isDirty, but it doesn't work as expected. The issue is that isDirty remains true even after reverting changes back to the original values. I think we have to compare old values and new values for this, do you any other idea?

Did you provide defaultValues? react-hook-form says it checks based on defaultValues.

We can solve the issue by checking the old and new values, but I don’t prefer this. react-hook-form already does this, so doing it again would mean extra work and unnecessary performance loss.

Hello @alicanerdurmaz,

You were absolutely right! After providing default values, isDirty now works as expected. However, I’m facing an issue where the isDirty state updates after watch().

In onValuesChange, I’m still getting the previous state of isDirty.

As shown in the attached image, I've added A in Content. The watch useEffect is triggered first, where isDirty is false. However, in the UserView example, isDirty is true, as expected.

I’ve done extensive debugging but still haven’t found a way to fix this. Do you have any ideas on this?

Hello @alicanerdurmaz,

You were absolutely right! After providing default values, isDirty now works as expected. However, I’m facing an issue where the isDirty state updates after watch().

In onValuesChange, I’m still getting the previous state of isDirty.

As shown in the attached image, I've added A in Content. The watch useEffect is triggered first, where isDirty is false. However, in the UserView example, isDirty is true, as expected.

I’ve done extensive debugging but still haven’t found a way to fix this. Do you have any ideas on this?

@mohit-2003 Is this isDirty state doesn't sync issue still ongoing?

Hello @alicanerdurmaz,
You were absolutely right! After providing default values, isDirty now works as expected. However, I’m facing an issue where the isDirty state updates after watch().
In onValuesChange, I’m still getting the previous state of isDirty.
As shown in the attached image, I've added A in Content. The watch useEffect is triggered first, where isDirty is false. However, in the UserView example, isDirty is true, as expected.
I’ve done extensive debugging but still haven’t found a way to fix this. Do you have any ideas on this?

@mohit-2003 Is this isDirty state doesn't sync issue still ongoing?

Yes @alicanerdurmaz, I did hours of debugging but didn't find any way to fix this. In my PR #6702, I am watching the isDirty state in a separate useEffect and updating setWarn there. This approach solves the issue.