Microsoft/TypeScript

Enum keys not accepted as computed properties if their name is not a valid identifier

開放

#25,083 建立於 2018年6月20日

 (3 則留言) (0 個反應) (0 位負責人)TypeScript (13,395 個分叉)batch import
BugDomain: enumGood First Issue

倉庫指標

星標
 (108,860 顆星)
PR 合併指標
 (PR 指標待抓取)

描述

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

貢獻者指南