User state after login doesn't contain req.user data about reactgo

[choonkending]

@joshhornby Hey I had a look into this. You can easily pass in the req.user object to be bootstrapped by alt.

Below is a horrid example:

// Naming convention leaves a lot to be desired
var user = req.user ? { object: req.user, authenticated: true, isWaiting: false } : { object: null, authenticated: false, isWaiting: false };

Whereas your Dashboard.jsx could be something like:

import React from 'react';
import UserStore from 'stores/UserStore';

export default class Dashboard extends React.Component {
  constructor(props) {
    super(props);
    this.state = UserStore.getState();
  }

  componentDidMount() {
    UserStore.listen(this._onChange);
  }

  componentWillUnmount() {
    UserStore.unlisten(this._onChange);
  }

  _onChange = () => {
    this.setState({
      user: UserStore.getState().user
    });
  }
  render() {
    console.log(this.state.user.get('object'));
    return (
      <div>Welcome to the Dashboard
        <div>{this.state.user.get('object').get('email')}</div>
      </div>

    );
  }
}

We'll be using AltContainer soon hopefully so none of this listen to stores for every high level component lol

[joshhornby]

@choonkending This still produces the same issue. After the intial login the user state only contains what has been set in the login action. Doing the example above doesn't work as undefined is returned when I do props.user.get('object') (I am already using AltContainer 👍 )

I will see if I can reproduce this bug this weekend and get an example repo online.

[choonkending]

@joshhornby Can you also have a look at #61? This is how I got AltContainer working.

[joshhornby]

Sure. I'll base my example repo off this.

Edit: On second thoughts no I'll get it working the old way and then update when the time comes!

[choonkending]

@joshhornby Closing as it's been quite a big change since then. Let me know what you think of the current redux :)