Workaround for string based enums in typescript

Question

So I found a suggestion that in typescript you can have string-based enums using this syntax:

export enum TextAlign {
    Left = <any>"start",
    Right = <any>"end",
    Center = <any>"middle"
}

Are there any drawbacks of using this approach?

There is a suggestion to use String Literal Type instead, although I find the enum more comfortable, as you can iterate through values.

The answers on stackoverflow.com/q/15490560/215552 have a lot of detail about using string-based enums. Is your question answered by those? Also, it does not appear as though you're asking for a workaround as your title suggests, but rather what the drawbacks are. — Heretic Monkey
– Heretic Monkey, Commented Jun 15, 2016 at 15:16

Jan Nielsen · Accepted Answer · 2017-02-27 18:26:39Z

1

Are there any drawbacks of using this approach?

Safety e.g.

let x:number = TextAlign.Left; // compiles fine but actually you just assigned a string to number

More

Every time you assert you are potentially lying to the compiler : https://basarat.gitbooks.io/typescript/content/docs/types/type-assertion.html and these lies tend to catch up :)

Jan Nielsen

12k16 gold badges76 silver badges137 bronze badges

answered Jun 16, 2016 at 0:23

basarat

278k61 gold badges475 silver badges528 bronze badges

Sign up to request clarification or add additional context in comments.