Task properties broken in canary

this commit changes the signature of ComputedProperty’s constructor to accept an array, so this passes the wrong arguments and throws a TypeError: Found non-callable @@iterator exception (although for some reason in CI I saw Assertion Failed: A computed property key must be a string, you passed undefined undefined instead).

I’m happy to take a crack at a PR to fix this, but I’m unsure of how. I’ll leave a comment in that commit asking the core folks if they have a recommendation, but the only two options I can think of are:

1. Base it an Ember version check (we’d want to verify that this will be released in Ember 3.8 first)
2. Use try...catch to invoke it one way, and on failure, try to invoke it the other way (seems pretty sketchy).

Other ideas?

[lypborges]

@balinterdi I just run

rm yarn.lock 
rm -rf node_modules 
yarn install

and fix the problem.

[pzuraq]

Also, for how to be compatible with multiple versions at once, we should use ember-compatibility-helpers, since it checks the Ember version at build time which allows us to completely strip out the unused version for folks who aren’t using that version.