TypeScript: Implicit number to enum cast

Question

Why does the following compile in TypeScript?

enum xEnum {
  X1,X2
}

function test(x: xEnum) {
}

test(6);

Shouldn't it throw an error? IMHO this implicit cast is wrong here, no?

Here is the playground link.

Answer 1

This is part of the language specification (3.2.7 Enum Types):

Enum types are assignable to the Number primitive type, and vice versa, but different enum types are not assignable to each other

So the decision to allow implicit conversion between number and Enum and vice-versa is deliberate.

This means you will need to ensure the value is valid.

function test(x: xEnum) {
    if (typeof xEnum[x] === 'undefined') {
        alert('Bad enum');
    }
    console.log(x);
}

Although you might not agree with the implementation, it is worth noting that enums are useful in these three situations:

// 1. Enums are useful here:
test(xEnum.X2);

// 2. ...and here
test(yEnum.X2);

And 3. - when you type test( it will tell you the enum type you can use to guarantee you pick one that exists.

Answer 2

No, it shouldn't. There is no type casting here, the base type behind them all is the same, integer.

typescript enum type checking works fine

Your complaint is about range value which, in this case, has nothing to do with type checking.

enum is a flexible set of constants

enum xEnum {X1=6, X2} // ruins it for test(0)