Andrey
Andrey
yes, makes sense On Tue, Aug 23, 2022 at 7:18 AM Paris Holley ***@***.***> wrote: > Because none has an any type, using eslint with the rule > @typescript-eslint/no-unsafe-argument will...
Use extend function. There is an example online for one of the extensions combined with many other extensions
Do not specify generic paratemers for hookstate function. Specify it one by one for extend function. See example here: https://hookstate.js.org/docs/extensions-snapshotable
Docs for extensions are pending updates. It is v4 feature and I have not finished with docs and overall battle testing, hence it is only RC version for now.
yes, it is v4 exception. It means you are switching a state source on rerender, ie. the initial value to useHookstate points to a different State on rerender. In code...
hmm... "It's causing hot module replacement in vite.js to fail." this should not be the cause... but when it throws this exception, what property do you acccess? what type is...
could you please create a reproducer repo? what state value do you provide to hookstate?
thanks. I will have a look later in the evening. It looks like Vite reloads globals but does not reload React state behind useState, which is clearly a problem, which...
local state is not impacted.. it is a global one i think... please let me know if it can be tuned...
Agree about adding deep readonly. Will make it happened. I disagree that noproxy should be allowed to be edited. This kind of changes for unwrapped by a proxy value are...