why contract function return value is changed?

[baixiaoyu2997]

before:

0: 0n
1: 0n
2: 10000000000000000000n
3: 4909593n
claimAmountUpdateBlockHeight: 0n
claimStakingAmount: 0n
currentStakingAmount: 10000000000000000000n
stakingAmountUpdateBlockHeight: 4909593n

now:

0: 0n
1: 0n
2: 10000000000000000000n
3: 4909593n

I don’t think it’s a version issue with ethers, I know that I can get the previous return value through toObject, but I want to know what happened

[ricmoo]

I’m guessing you mean between v5 and v6?

In v6, the Result object is a proper subclass of Array wrapped in a proxy. The keys still exist; e.g. result.claimStakingAmount will still work.

You can also use result.toObject() to dump out a named version of the object. :)

[ricmoo]

(note the difference is more that console.log isn’t good at knowing what properties to expose on Proxy objects, but since v5 couldn’t use proper Proxy, it just set a bunch of object properties on generic objects)

[baixiaoyu2997]

thanks for you reply, I have been using 6.9.x recently, but the console did not report an error indicating that a certain attribute is missing. This problem only appeared today. This is really strange, and if I want to modify it to use toObject , an error will also be prompted because the return type lacks this method.
I use typechain to add types to contract instances

nvm I think this is not a problem with ethers. I will research it myself.

[baixiaoyu2997]

It turns out that it was caused by my destructuring the return value.

useContract()
    .userDatas(address)
    .then((res) => {
      const { bHODLEntryAccuReward, ...resCopy } = res //  reference to become invalid
    })