You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected behavior:
Not compiling. You cant define a type based on what is currently define in the array.
This behavior broke the strict null check validation because this value should be undefined or the accessor non legit.
Actual behavior:
Compile and value as the type of all types defined in the tuple, in this case string | number.
Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.
Activity
imcotton commentedon Sep 5, 2017
from: handbook#tuple
sebdoucet commentedon Sep 5, 2017
Because it's in the hanbook, that does not make more cense to me.
Why it's not at least a tuple combine with undefined. It broke strict null checking like
string | number | undefinedmhegazy commentedon Sep 5, 2017
Duplicate of #6229
mhegazy commentedon Sep 20, 2017
Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.