Questions about the behavioral change of Persist middleware

[limuen]

Thank you very much to the author for creating such an excellent library as zustand. After upgrading to V5 version according to the documentation, even if I don't need it
useUserStore. setState (){
token: null,
loginToRoute: "setState"
});，
But I can still get the default parameters I set locally. Is it because I'm using the wrong posture?

repoUrl: limuen/monorepo-project@5760d8a#diff-224dbaccff558cc5afb7c40e26b5e9d729073d197b70dcb2788918d388532233

Looking forward to your reply, thank you

[dbritto-dev]

@limuen I don't get your point

[limuen]

@limuen我不明白你的意思

Doesn't the V5 version say that persists must have a setState? I can persist without setState

[dbritto-dev]

https://zustand.docs.pmnd.rs/migrations/migrating-to-v5#persist-middlware-no-longer-stores-item-at-store-creation

[limuen]

https://zustand.docs.pmnd.rs/migrations/migration-to-v5#persist-middlware-no-longer-stores-item-at-store-creation

So after upgrading to v5, I don't have useCountStore.setState, but I can still get the initialization status

[dbritto-dev]

@limuen after upgrading to v5 you have to use to setState() to persist the initialState.

useUserStore.setState(state => state)