Comments (8)
you should be able to set the initialState variable
const initialState = { ... }
const [useStore, api] = create(set => initialState)
api.setState(initialState)
from zustand.
@laurib Unfortunately, Zustand's set
doesn't allow this right now. I guess the best option is to store all your state in a property and overwrite that property. That's kind of messy but I think a create
wrapper can abstract this for you:
import create from "zustand";
function createNoMerge(stateCreator) {
let setState;
let getState;
const [useStore, api] = create((set, get) => {
setState = newState => {
const oldState = get().state;
const state =
typeof newState === "function"
? newState(oldState)
: newState;
return set({ state });
};
getState = () => get().state;
return {
state: stateCreator(setState, getState)
};
});
api.setState = setState;
api.getState = getState;
const useStoreNoMerge = (sel = s => s, ...args) => {
const selector = () => sel(getState());
return useStore(selector, ...args);
};
return [useStoreNoMerge, api];
}
const [useStore, api] = createNoMerge(() => ({
a: 1,
b: 2
}));
from zustand.
Are there any plans to change set
to support this?
Thanks in advance!
from zustand.
@MrFungusEli I would like the default behavior of set
to overwrite instead of merge. That would be a breaking change though.
from zustand.
wouldnt overwrite require full reducers though? like when you just want to change a single value.
state { a: 1, b: 2, c: 3 }
set({ a: 0 }) // ---> { a: 0 } ?
that would make set(value) quite useless except for resets, since you would always need the function form: set(state => ...).
from zustand.
Is there anything I can do to help? I'm wondering if this would be a good first time contribution for me :)
from zustand.
i guess making it merge or not is a small change, but the repercussions of how it effects all purposes and use cases isn't clear to me. from my experience, resetting a set of objects is rare, i solve it via intialState. plain deletion i haven't ran into. merging, or set(value) instead of set(function) on the other hand is something i do often - i realize this could just be me.
if the change would make set(value) obsolete because it would now delete all data except the one prop that it gets, and set(function) would always have to spread, then i think it needs a bigger discussion involving more users. we should also look into what made react go for setState and useState as a merging op.
alternatives would be middleware or set(arg, merge=true)
from zustand.
you should be able to set the initialState variable
const initialState = { ... } const [useStore, api] = create(set => initialState) api.setState(initialState)
I must have missed this, this works absolutely fine for me. Thanks!
from zustand.
Related Issues (20)
- Website graphics rendering issues (Linux) HOT 3
- shallow not support nested object HOT 1
- Are these two methods exactly the same? HOT 1
- Itβs not recommended to suspend a render based on a store value returned by useSyncExternalStore.
- RFC: How is v5-alpha? HOT 11
- should useShallow add into the documents?
- Can't use persist with context implementation mentioned in the docs for Next.js HOT 1
- Re-render issue while performing open and setOpen using shadcn
- Re-render issue while performing open and setOpen using shadcn HOT 1
- type WithoutCallSignature<T>
- docs: Add suggestions about getInitialState on persist
- Cant user Array of Map type to store data
- overview of the zustand API HOT 1
- Persist storage : values are converted to strings before replacer
- Value is empty on initial render and sets after few milliseconds
- Immer Middelware Typescript error: Exported variable 'useMyStore' has or is using name 'WritableDraft' from external module "../node_modules/immer/dist/immer" but cannot be named.
- blacklist and whitelist
- Argument of type '(state: ClientStore) => Client | undefined' is not assignable to parameter of type 'ClientStore | Partial<ClientStore> | ((state: ClientStore) => ClientStore | Partial<ClientStore>)'. Type '(state: ClientStore) => Client | undefined' is not assignable to type '(state: ClientStore) => ClientStore | Partial<ClientStore>'. Type 'Client | undefined' is not assignable to type 'ClientStore | Partial<ClientStore>'. Type 'undefined' is not assignable to type 'ClientStore | Partial<ClientStore>'.ts(2345)
- The value I save to storage with persist is delayed when the page refreshes.
- State updated in one component but not in another one
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from zustand.