-
|
I have some components whose state are not supposed to be null in their life time. What is the workaround this? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
Do you mean how to add type definition for it? If you mean the actual value you can implement your own base component type and set the state in constructor and extend everything from that type. |
Beta Was this translation helpful? Give feedback.
-
|
Hmm why the component's state can be null anyway? In my application it is never supposed to me? So why it has been implemented like that in Inferno? |
Beta Was this translation helpful? Give feedback.
-
|
Default state is null for react compatibility. So npm packages made for react works with inferno too |
Beta Was this translation helpful? Give feedback.
-
|
Okay. How am I supposed to check for this in typescript? Always do |
Beta Was this translation helpful? Give feedback.
-
|
If you initialize your state to some object in components constructor, then you can declare the state non nullable. See the example I linked in previous comment.
Yes, all the same practices from JS apply to TS too |
Beta Was this translation helpful? Give feedback.
Do you mean how to add type definition for it?
See:
inferno/packages/inferno/__tests__/hooks.spec.tsx
Line 22 in b300a89
If you mean the actual value you can implement your own base component type and set the state in constructor and extend everything from that type.