Suggestion
🔍 Search Terms
✅ Viability Checklist
My suggestion meets these guidelines:
⭐ Suggestion
Since pattern literal types like `${number}` are valid as of #40598, I feel like there should be an option to make:
type ArrayLikeKeys = keyof ArrayLike<any>;
result in:
type ArrayLikeKeys = "length" | `${number}`;
The same should happen for any numeric property key:
interface Foo {
1: "a";
2: "b";
3: "c";
}
// Currently is: : 1 | 2 | 3
// Should be: "1" | "2" | "3"
type KeyOfFoo = keyof Foo;
// Currently is: never
type StrictKeyOfFoo = (keyof Foo) & (string | symbol);
like with:
interface Foo {
"1": "a";
"2": "b";
"3": "c";
}
// Is: "1" | "2" | "3"
type KeyOfFoo = keyof Foo;
📃 Motivating Example
This makes keyof and numeric index signatures match runtime behaviour.
💻 Use Cases
Currently, it’s necessary to use the strictKeyof and StrictPropertyKey helpers:
type strictKeyof<T> = keyof T extends infer K
? (K extends number ? `${K}` : K)
: never;
type StrictPropertyKey = string | symbol;
Relevant issues:
This will most likely depend on #26797, so that treating numeric index signatures as numeric pattern literal index signatures is valid:
interface ArrayLike<T> {
readonly [index: `${number}`]: T;
readonly length: number;
}
Suggestion
🔍 Search Terms
✅ Viability Checklist
My suggestion meets these guidelines:
⭐ Suggestion
Since pattern literal types like
`${number}`are valid as of #40598, I feel like there should be an option to make:result in:
The same should happen for any numeric property key:
like with:
📃 Motivating Example
This makes
keyofand numeric index signatures match runtime behaviour.💻 Use Cases
Currently, it’s necessary to use the
strictKeyofandStrictPropertyKeyhelpers:Relevant issues:
ProxyHandler#35594 (comment), fix(lib/es2015): Fix definition ofProxyHandler#35594 (comment), fix(lib/es2015): Fix definition ofProxyHandler#35594 (comment)Reflectmethods #41987This will most likely depend on #26797, so that treating numeric index signatures as numeric pattern literal index signatures is valid: