lore-generate-new/templates/esnext/src/components/Master.js

Generates a new Lore application

/**
 * This component serves as the root of your application, and should typically be the only
 * component subscribed to the store.
 *
 * It is also a good place to fetch the current user. Once you have configured 'models/currentUser'
 * to fetch the current user (by pointing it to the correct API endpoint) uncomment the commented
 * out code below in order to fetch the user, display a loading experience while they're being
 * fetched, and store the user in the applications context so that components can retrieve it
 * without having to pass it down through props or extract it from the Redux store directly.
 */

import React from 'react';
import PropTypes from 'prop-types';
import { connect } from 'lore-hook-connect';
import PayloadStates from '../constants/PayloadStates';
import RemoveLoadingScreen from './RemoveLoadingScreen';
import '../../assets/css/main.css';

@connect(function(getState, props) {
  return {
    // user: getState('currentUser')
  };
}, { subscribe: true })
class Master extends React.Component {

  // static propTypes = {
  //   user: PropTypes.object.isRequired
  // };

  // static childContextTypes = {
  //   user: PropTypes.object
  // };

  // getChildContext() {
  //   return {
  //     user: this.props.user
  //   };
  // }

  componentDidMount() {
    // If you want to play with the router through the browser's dev console then
    // uncomment out this line. React Router automatically provides 'router'
    // to any components that are "routes" (such as Master and Layout), so this
    // is a good location to attach it to the global lore object.

    // lore.router = this.props.router;
  }

  render() {
    // const { user } = this.props;

    // if (user.state === PayloadStates.FETCHING) {
    //   return null;
    // }

    return (
      <div>
        <RemoveLoadingScreen />
        {React.cloneElement(this.props.children)}
      </div>
    );
  }

}

export default Master;