mutate function doesn't behave the same in v2.1.5 vs v1.3.0

[george-van-heerden]

EDIT: Apologies, the issue I was facing was not due to SWR 🙈

Hi everyone :)

I'm upgrading all our dependencies on our project, and noticed something that I'm not 100% sure how to resolve.

Previously in v1.3.0:
After we have updated a record, we simply called mutate(<key>), then the records would be updated. Even the nested values inside of the record.

Now in v2.1.5:
mutate(<key>) doesn't seem to fully (deeply?) update a mutated record. The record's properties are updated, but the nested object's values aren't updated.

So I had a look in the docs and implemented Update Cache After Mutation like this:

     mutate(updatedRecord, {
        populateCache: (updatedRecord, records) => {
          const filteredRecords = records.filter(
            (record) => record.id !== updatedRecord.id
          );
          return [...filteredRecords, updatedRecord];
        },
      });

And now the mutated record is updated as we would expect, but that record's element is now removed from the list of elements and reappended. So it looks jerky. I'm sure this can be fixed by using useDefferedValue, but I was just wondering if I missed something when I went through the change logs and docs or if I am misunderstanding how to use this feature.