Fails if there are 'classic' classes present

[mfeckie]

If used in a mixed project (like one transitioning to typescript), fails hard when tasks are present in classic classes.

For example

  test('Classic class', async function(assert) {
    const subject = EmberObject.create({
      testTask: task(function*() {
        yield timeout(1);
      }),
      async perform() {
        await timeout(1);
        return 'done';
      }
    })

    const value = await subject.perform();
    assert.equal(value, 'done');
  });

results in

Build Error (broccoli-persistent-filter:Babel > [Babel: ember-concurrency-typescript]) in dummy/tests/unit/task-test.ts

/addons/ember-concurrency-typescript/dummy/tests/unit/task-test.ts: `task` has to be a direct child of a `ClassProperty`.
  30 |   test('Classic class', async function(assert) {
  31 |     const subject = EmberObject.create({
> 32 |       testTask: task(function*() {

[buschtoens]

Hey @mfeckie!

I'm sorry, that I didn't update the README yet and probably cost you some time. ember-concurrency-typescript was an experiment that I'll likely not pursue any longer. Instead we're trying to get machty/ember-concurrency-decorators#56 out the door, which is essentially almost the same, but a bit better in some regards.

[buschtoens]

I published a pre-release, so you can try it out already: machty/ember-concurrency-decorators#56 (comment)

[mfeckie]

Don't apologise 😄 Didn't really waste my time! I was just experimenting with options and now I can try the alpha :)