Separate Client and Server Actions?

[ronag]

No description provided.

[steida]

Actually, not needed ;-) facebookarchive/flux#172

[ronag]

No I mean. The way it is now we can't have "media client" actions and "media server" actions in separate files which is a requirement for avoiding circular imports.

i.e. a common pattern is:

user client action -> webapi -> user server action

e.g.

// Client Actions

export function createUser(name:String) {
   WebApi.createUser(name)
   dispatch(createUser, name)
}

// WebApi

export function createUser(name:String) {
  // ...
}

// Server Actions

export function createdUser(id:String) {
  dispatch(createdUser, id)
}

[steida]

PR please.

[ronag]

I don't have any good suggestion for solution. Just pointing out a problem.

[steida]

I am not aware of this issue yet, maybe it's not problem with ES6 modules. Let's wait.