Additional helpers? about rfcs HOT 5 CLOSED

@NullVoxPopuli I think for the examples you give here, having #756 plus a fix to make method dispatch work as expected would solve nicely. You can import noop (or define it) easily enough, and something like flat would "just work" as an instance on the array itself:

let someArray = [[1], [2]];

<template>
  {{(someArray.flat)}}
</template>

(In general, my own inclination is to have Ember focus on the things it specifically brings to the table, while letting lodash etc. handle general JS utility behavior.)

from rfcs.

I’m closing since there doesn’t seem to be a path forward. However, I will happily reopen if one is proposed!

from rfcs.

Using @chriskrycho's suggestion,
atm, with methods on objects, we get an error: Uncaught (in promise) TypeError: can't convert undefined to object

Repro here

from rfcs.

Yep, what we need is to see if we can fix method handling so it works the way people expect it to. Namely: if you actually have a reference to an object and call a method on it, that should work, just like in JS. The spec group has talked about this a few times and come up with some possibly workable ideas but we need someone with the relevant knowledge to champion and drive forward that work.

from rfcs.

(To clarify, I don’t mean “someone from the community needs to volunteer,” though if someone does that’s awesome and we would try to help get them leveled up. But even on Framework the list of folks with expertise in the Glimmer syntax and semantics needed to drive this and time to work on it specifically is short at present.

from rfcs.