SetState & GetState Typescript declaration in create function arguments (bis) about zustand HOT 4 CLOSED

#49 fixes this issue a far as I can see. I close the current issue. Thanks a lot.

from zustand.

The fix works fine with a very basic sample like this one :

But I'm afraid that th fix is not enough because it is very easy to get a non working case. Imagine you have several stores, and imagine you want to do something generic on them. You will create a function that performs the "generic" things and then call that function for each store you have.

This will lead you to create a generic function that encapsulates the zustand create function invocation. But as far as I can see, it doesn't work.

Just take a look at this really trivial sample in which we try to do something generic during store intialization :

I hope you will agree with me that this sample code is trivial (10 lines of effective code), and it highlights the problem...

In other words, as soon as you want to add even a thin layer over zustand for your own purpose in Typescript world, you meet that problem.

I have put all this (trivial) code on codesandbox : https://codesandbox.io/s/j2nys
(basic.ts and initStore.ts files)

from zustand.

Another way to present the problem is that today, it is not possible to extend zustand using typescript. Because anybody that would like to extend zustand will quickly have to create a generic function that encapsulates zustand createfunction.

And the keyof TState extends never part of the typescript definition prevents from being able to do that:

export default function create<TState extends State>(createState: keyof TState extends never ? StateCreator<State> : StateCreator<TState>): [UseStore<TState>, StoreApi<TState>];

from zustand.

I can't find a way to allow extending create and keep inference working when not explicitly passing the type of State. I'll just allow inference to fail instead of trying to jump through hoops to get it working.

from zustand.