"non-string literal property keys not supported"

[redchair123]

var x = {
    1234:"a",
    5678:"b"
}

Flow generates an error per integer key.

According to 11.1.5 of ECMA-262 this is a perfectly valid construct.

EDIT: @jgrund 's solution in #380 (comment) works well

[fatboysuns]

I get the same error when I when I run it on a jquery javascript.
$.ajax({
url: url,
dataType: 'html',
success: function(data) {
//do something
},
error: function(data) {
// something else
},
// This is the line Flow complains
statusCode: {
404: function() {
alert('404');
}
}
});

[gabelevi]

Number literals are annoying, since we need to canonicalize them. We should probably just bite the bullet and implement the algorithm. CC @mroch

[julianacipa]

Any update on this issue?

[Zaba999]

👍 Is there any progress with this issue? I really need this one :)

[jgrund]

As a really awful hack:

var x = {
    [1234]:"a",
    [5678]:"b"
}

[rosskevin]

ugh. I too need this.

[StreetStrider]

The issue still bothers. Tried to typecast to something like {[n: number]: mixed} — not working. Even if it did, it's such a crazy workaround for such a small thing.

[redchair123]

Any progress?

[punmechanic]

Playing devils advocate here: All keys on an object will be implicitly converted to a string. I like that this error is explicit about that behaviour (even if the error is not very well defined).

EDIT: 2016 me was an idiot and incorrect. This behaviour is surprising and unintuitive

[lenovouser]

Any plans to fix this? This should't throw an error