got 'Property is always "undefined"' when it's not always "undefined"

[thecotne]

type AA = {
    a:? number,
    b:? number,
    c:? string,
}

const a: AA = {};

if(a.a !== undefined && a.b !== undefined && a.c !== undefined) {// error: Property is always "undefined"

}

try

[artanik]

Found a temporary solution. It doesn't fix the bug though. You can wrap the first condition in parentheses.

type AA = {
    a:? number,
    b:? number,
    c:? string,
}

const a: AA = {};

if((a.a !== undefined && a.b !== undefined) && a.c !== undefined) {
    
}

This is better than ignoring bug with // @hegel-issue comment.

Try.

[trusktr]

That's interesting (and sorry, off topic), the syntax c:? string, doesn't seem to be compatible with TS (not sure if that's a goal). In TS it is c?: string, (example).

[thecotne]

@trusktr it's flow's syntax...

[trusktr]

Do you guys like Flow better than TypeScript? (Just curious)

TypeScript seems to have higher usage, so if Hegel syntax is more aligned with TS, then easier for people to migrate to and adopt Hegel.

[JSMonk]

Oh, just fixed it, so it will work in the new Hegel version.