Color Names

[BobFrankston]

Typing color names is risky since there is no checking for typos. It would be nice to have named colors as in Color.Wheat or something like that. Even nice would be to type a field like backgroundColor typechecked as an HTML color though I'm not sure how to do that while keeping fully compatible with JS.

For an application that had only a limited number of valid colors I created a static class
class Kolor {
static black: string = "black";
static silver: string = "silver";
static gray: string = "gray";
..
}
it didn't solve the type checking but did reduce typos.

[iam3yal]

In my opinion, you should use enum instead of a class for that where each member in the enum will have a numerical representation of the color instead of string, it's better for many reasons.

http://www.typescriptlang.org/Handbook#basic-types-enum

[BobFrankston]

I do use enums but in this case the color names are string and I'm using them as strings. If I used an enum I'd have a more awkward syntax in converting to strings explicitly every time. (Were this C# I could get far fancier for better or worse).

[basarat]

I do use enums but in this case the color names are string and I'm using them as strings.

Here's what I've done commonly (taking advantage of TypeScript's type inference on assigment to infert the type of colors):

let colors = {
   red : 'red',
   blue: 'blue',
  // so on
}

Now :

colors.blue; // okay 
colors.invalid; // Error

[BobFrankston]

Thanks. That's a reasonable solution. The only point I'm making is that this should part of the standard Typescript offering because it's so fundamental to doing HTML5.

[basarat]

There is this issue : #3192

[danquirk]

Yeah, dupe of the mentioned string enums issue.