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
Seems like the TS team's reasoning for making their official Omit non-strict included the fact that Extract was also non-strict, which is something I just ran into wanting. Just like OmitStrict, ExtractStrict will get the compiler to help out during refactoring things like this, or to prevent typos in the string keys:
exporttypeTSomeColorOptions=ExtractStrict<TColor,'blue'|'whitee'>// should error for typo
The text was updated successfully, but these errors were encountered:
Any interest / reason to not want this type added? I can make a PR if so:
context:
Seems like the TS team's reasoning for making their official
Omit
non-strict included the fact thatExtract
was also non-strict, which is something I just ran into wanting. Just likeOmitStrict
,ExtractStrict
will get the compiler to help out during refactoring things like this, or to prevent typos in the string keys:The text was updated successfully, but these errors were encountered: