Scrap Marty.Component in favour of Marty.createContainer

[jhollingworth]

FB just blogged about how Relay works.

This makes a lot of sense and gets around a load of the issues with Marty.Component (e.g. contextTypes, having to inherit from a base class).

I suggest we scrap Marty.Component altogether and just replicate Relay.createContainer

class User extends React.Component {
  render() {
    return this.props.user.when({
       ...
    });
  }  
}

module.exports = Marty.createContainer(User, {
  listenTo: UserStore,
  user() {
    return UserStore.getUser(123)
  }
});

[bigardone]

So this means that:

• Components will use props received from containers instead of state.
• Stores state changes will affect containers.
• State mixins are not longer needed.

Is this right?

[jhollingworth]

Yeah, spot on. It provides a clear separation with between the component and fetching state (no more when in you're components) plus opens some more complex scenarios (e.g. only certain properties are needed before rendering, setting default values when pending, etc).

The PR has an expanded example of how its going to look.

[jhollingworth]

Although, I should say state mixins aren't being depreciated just yet (maybe v0.11). We're just recommending you use containers as they are better.

[bigardone]

Awesome, it looks really useful.