circular dependency between action and webapi about alt HOT 7 CLOSED

If you're using commonjs you can use exports to get around this:

alt.createActions(ActionClass, exports)

from alt.

Another option is to use a callback.

class Actions {
  constructor() {
    this.generateActions('actionOne');
  }

  actionTwo() {
    WebAPIUtils.someAsyncOp((err, data) => {
      this.actions.actionOne(data);
    });
  }
}

from alt.

@goatslacker - thanks, that worked! Can you explain what happens behind the scenes when using alt.createActions(ActionClass, exports) ?

@troutowicz , that was the approach I was going to take as last resort, but I like goatslacker's solution better.

from alt.

The docs mention what that 2nd parameter is for: https://github.com/goatslacker/alt/blob/master/docs/createActions.md#createactions

Essentially it'll just add each action to exports. You can pass any object into createActions as its second parameter and it'll add all the actions to that object.

action.foo becomes exports.foo

Does that answer it or were you looking for a why does this work in commonjs when you use exports but not module.exports?

from alt.

I'm more curious as to why it works, but doesn't when I use module.exports.

from alt.

@jongbeau Here is a relatively short article that should help explain what is happening under the covers.

Note that not all module systems do a great job at handling circular dependencies. I typically use webpack as it handles circular dependencies well and just like Node (in the way described in the article above).

from alt.

Oh interesting didn't know that tidbit.

It works because the values get assigned to exports later on so they'll be available at run-time when you need them.

from alt.