Flow: $NonMaybeType<mixed> still takes `null` and `undefined`

[mrkev]

try flow

This is probably a bug. ~It would make a good first task.~ _Edit: maybe not._

[motiz88]

Could be related: $NonMaybeType<$Shape<T>> likewise still takes null and undefined. Example case

If anyone's curious, there _is_ a workaround in the form of $Shape<T> & Object.

[lucianomlima]

Still doesn't work with version 105.2.
Try Flow

[goodmind]

@lucianomlima your example is wrong, $NonMaybeType isn't used for objects
Try Flow

[lucianomlima]

@goodmind what I can do or use with Objects?

[goodmind]

@lucianomlima for your case Try Flow

[lucianomlima]

@goodmind Thanks a lot!

[goodmind]

@mrkev it's actually pretty hard to fix... I didn't knew about ground_subtype function and $NonMaybeType<string> is reverse of ?string type and uses bunch of new use_ts for me ReposUseT and stuff. IDK if this is good first issue 😬