Error in Index Signature Assignment about typescript HOT 3 OPEN

I'm interested in seeing how this goes. I am also surprised that excess property checking would kick in here, or that there's seemingly no previous mention of this behavior in GitHub. It seems like such an obvious bug that surely people have encountered it before? What am I missing here?

from typescript.

My first thought was that maybe in an object literal all indices are treated as strings (as opposed to an array literal where you have implicit numeric indices). But if you remove the string index signature, the error goes away. So I guess you could say a string index signature takes precedence in an object literal, but whether that's by design or a bug... ¯\_(ツ)_/¯ dunno

from typescript.

I'm not 100% sure this is "fixable" in a great way, but someone can certainly try.

Previous issues have complained about inconsistencies between { 1: expr } and { "1": expr }, which "should" be identical since they have actually-identical runtime semantics, but the intent of this code is quite clear, plus the equivalent assignment works:

// ok
testObj[1] = { tKey: "tVal", sKey: "sVal" };

from typescript.