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
Describe the bug
When using a union of string, number or boolean values, the types ultimately resolve back to the base type.
To Reproduce
Steps to reproduce the behavior:
typeOperatingState='good'|'bad'|'alright';interfaceThing{readonlystate: OperatingState}// FormControlState<string>, should be FormControlState<OperatingState>typeBad=FormGroupState<Thing>['controls']['state'];
[If possible, please also provide a reproduction repository or fork this code sandbox and reproduce the issue there.]
Expected behavior
The union type should be retained.
Screenshots
[If applicable, add screenshots to help explain your problem.]
Library version:
7.0.0
Additional context
It seems like we could take advantage of some of the newer TS features in 4.7+ to achieve this:
Describe the bug
When using a union of string, number or boolean values, the types ultimately resolve back to the base type.
To Reproduce
Steps to reproduce the behavior:
[If possible, please also provide a reproduction repository or fork this code sandbox and reproduce the issue there.]
Expected behavior
The union type should be retained.
Screenshots
[If applicable, add screenshots to help explain your problem.]
Library version:
7.0.0
Additional context
It seems like we could take advantage of some of the newer TS features in 4.7+ to achieve this:
The same treatment could be applied to number and boolean.
The text was updated successfully, but these errors were encountered: