Microsoft/TypeScript
Ver no GitHubEnum keys not accepted as computed properties if their name is not a valid identifier
Open
#25.083 aberto em 20 de jun. de 2018
BugDomain: enumGood First Issue
Métricas do repositório
- Stars
- (48.455 stars)
- Métricas de merge de PR
- (Mesclagem média 6d 17h) (9 fundiu PRs em 30d)
Description
TypeScript Version: 2.9.2
Search Terms: computed property name
Code
enum Type {
Foo = 'foo',
'3x14' = '3x14'
}
type TypeMap = {
[Type.Foo]: any
[Type['3x14']]: any
}
Expected behavior:
Type['3x14'] to be usable as a computed key in a type definition.
Actual behavior:
A computed property name in a type literal must refer to an expression whose type is a literal type or a 'unique symbol' type.
This is the case even for Type.Foo if it's written as Type['Foo'] instead; so it seems there is some early bailout when the bracket operator is involved. For certain key names it may not be possible to write them without resorting to brackets, like a name that starts with a digit.
Playground Link: Link