Open smtchahal opened 2 years ago
@smtchahal Please replace type MyComponentProps
with:
type MyComponentProps = {
name: string
}
And it will work fine!
@peakchen90 Of course it will, but the point is, sometimes the requirements are such that the type just needs to be nullable or optional. When that's the case, the following will work fine with TypeScript:
const MyComponent = ({ name }: MyComponentProps) => (
<>
name && <MyName>{name}</MyName>
</>
)
If this is okay with TypeScript, then x-if
should also be okay.
@smtchahal I mean this has nothing to do with x-if
, it's the default behavior of Typescript
@smtchahal Oh, I understand, but maybe I cannot do something for it... It just a babel plugin
Describe the bug TypeScript does not understand x-if. Inside an
x-if
block, the passed variable should be evaluated for truthyiness, but it is not.To Reproduce Steps to reproduce the behavior:
The following code should do it:
Expected behavior TypeScript compiles successfully and does not show any errors.
{name}
gets passed as a string to<MyName>
.Actual behavior TypeScript complains that
<MyName>
requireschildren
to be of typestring
, butstring | null
was passed.Environment