-
Notifications
You must be signed in to change notification settings - Fork 107
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
State.nested
does not work with symbol
keys
#374
Comments
This library is dead, there is no support and there is no traction. |
It's important to remember that this library is being developed by a single developer, most likely in his spare time. He may have other responsibilities or priorities that prevent him from working on the project as often as you would like. You always have the option to contribute or fork. |
Hi, guys the library is not dead. I am on holidays offline at the moment. I
had the busiest year working for the fastest growing start up in NZ history
and needed a good break offline to recover. I will address all the tickets,
no worries
…On Sat, 28 Jan 2023, 02:15 zroug, ***@***.***> wrote:
It's important to remember that this library is being developed by a
single developer, most likely in his spare time. He may have other
responsibilities or priorities that prevent him from working on the project
as often as you would like. You always have the option to contribute or
fork.
—
Reply to this email directly, view it on GitHub
<#374 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA6JSVIK4MKZRP5HJHVI2GLWUPDA3ANCNFSM6AAAAAATVWQA6M>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Symbols are possible to get and set on a state and state value. They are actually special and maybe used by plugins to associate hidden metadata. I will explore if it is possible to prevent the use case of nested(symbol) on a type system. If you can come up with type definition which traps it, it would be great. |
Expected output is
Hello World!
, actual output isundefined
, there is no runtime error or type error from TypeScript.Hookstate should do one of two things:
symbol
keysIn this case, this should cause a type error for TypeScript and maybe a runtime error with a readable error message.
symbol
keysThe latter is of course preferred but more difficult to achieve.
The text was updated successfully, but these errors were encountered: