Microsoft/TypeScript
GitHub ã§èŠãwrong behavior about type parameters of `as` clause in a mapped type
Open
#59,713 opened on 2024幎8æ22æ¥
Domain: Mapped TypesHelp WantedPossible Improvement
Repository metrics
- Stars
- Â (48,455 stars)
- PR merge metrics
-  (å¹³åããŒãž 6d 17h) (30d ã§ 9 merged PRs)
説æ
ð Search Terms
type parameter as mapped type
ð Version & Regression Information
5.7.0-dev.20240821
⯠Playground Link
ð» Code
type IsString<T> = T[] extends string[] ? true : false
type OmitStringKey<T extends object> = {
[K in keyof T as IsString<T[K]> extends true ? never: K]: T[K]
}
function f<T>(t: T): { data: T } {
type A = IsString<T> // deferred
type B = A extends true ? true : false // deferred
type C = IsString<{data: T}['data']> // deferred
return {} as OmitStringKey<{ data: T }> // `data` is omitted
}
ð Actual behavior
OmitStringKey<{ data: T }> omit data property. That means IsString<T> extends true in the as clause is true, while T is not decided yet.
ð Expected behavior
type evaluation should be deferred
Additional information about the issue
No response