Martin Muñoz

`array2.[index]` already means something. It's would be breaking to change it. We could consider `array2[index]`.

@egemon This should have been closed as working. What's the issue you're running into? You should be able to use `(get array index)` in Ember to fetch an array index.

Possibly related https://github.com/emberjs/ember.js/pull/15366

This is a default feature of the Handlebars parser. We can disable it but it is a breaking change. See https://github.com/wycats/handlebars.js/issues/1072 and https://github.com/wycats/handlebars.js/commit/ea3a5a1.

We already lookup helpers for curlies that appear outside of attributes: https://github.com/tildeio/htmlbars/blob/master/packages/htmlbars-runtime/lib/hooks.js#L698. Doing it for attributes as well is the correct thing to do. That said, I don't like this...

Shouldn't babel be handling this?

Track is a void element so this behaviour is "expected". We could provide a better error message. It sounds like a bug if `outerHTML` behaves that way. Is it relevant,...

@supernullset I'm not sure if this is defined in the html5 spec, but either way we definitely want to match what the major browsers are doing. We should also give...

Actually, I think this should be handled early on in the parsing / AST generation stage.

It's not invalid syntax. Anyways, Esprima parses `{x:1,x:2}` as two properties so let's stick with your way. We don't have a system for warnings yet.