-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Support for Zustand 4.5.0+ and Introduce Mutative Middleware #92
Conversation
🦋 Changeset detectedLatest commit: 2fa1da9 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Awesome! I'll let you add the major changeset, then I'll release this. |
Just need to fix the CI now. |
@zbeyens can you start the last workflow? |
Thanks! |
set: TStoreApiSet<StateType, Mutators, TActions>, | ||
get: TStoreApiGet<StateType, Mutators, TSelectors>, | ||
api: TStateApiForBuilder<StateType, Mutators, TActions, TSelectors> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@imarabinda README has extendSelectors((state, get, api)
, should we update it and add the missing breaking change in the changelog?
Description
This PR addresses the compatibility issue with zustand version 4.5.0 and above. It includes the following updates:
mutative
support. Passmutative: true
in the options.Migration Instructions
Update the Store Initialization:
Replace the old method of initializing the store with the new API.
or
Ensure to pass the configuration object with name and other options as needed.
If your application relies on immer, enable it by passing immer: true in the configuration object.
With the new version, integrating middlewares has also changed. Here's how to upgrade your middleware usage: