React 16 upgrade [WIP]

[tlrobinson]

Superseded by #6756 #6757 #6758

Upgrade some dependencies to allow upgrading to React 16. Haven't tracked down all dependencies causing warnings, yet.

• update misc dependencies
• remove instances of createClass
  • react-sortable
• remove instances of React.PropTypes
  • react-sortable
  • redux-auth-wrapper
  • redux-form
• replace react-sortable
• fix element disappearing while dragging
• upgrade React to 16
• fix or catch errors in lifecycle methods
  • catch errors in App as a fallback
    • better designed generic error page, paging @mazameli @kdoh
  • catch errors in Visualization
  • UserAvatar incorrect merging of styles
  • constrainToScreen shouldn't crash if null element is passed
  • TableInteractive cell measuring code uses ReactDOM.unstable_renderSubtreeIntoContainer
• replace ReactDOM.unstable_renderSubtreeIntoContainer with ReactDOM.createPortal where possible
  • BodyComponent
  • Modal
    • WindowModal
    • FullPageModal
  • Popover
• fix tutorial
• fix hot reloading, if possible

Issues I've found migrating tests to Enzyme v1 and React v16:

• needs app.update() in some places, in particular after store.waitForActions() in integration tests
• element.find() doesn't include the element itself
  • for checking classes it's better to do element.hasClass("...") etc
  • possibly related: select.find(Popover) (or children of Popover) no longer works, but app.find(Popover) may

[tlrobinson]

If anyone wants to pick this up I'm not going to be able to work on it for a couple weeks.

[tlrobinson]

Ok I've upgraded to React 16, but it still needs a ton of testing due to how React 16 error handling works. Basically React 16 gives you a chance to handle errors thrown in render and other lifecycle methods, but by default it just unmounts the entire app to avoid possibly displaying corrupt data.

So we need to find and fix some bugs that weren't previously a big deal.

We can also add componentDidCatch to certain components to limit the effects of crashes. I added componentDidCatch to the root App component so we can at least display a message apologizing to the user and asking them, to refresh (or hit a button to refresh, or whatever). We can also use this to isolate errors in visualizations better.

Read more here https://reactjs.org/blog/2017/07/26/error-handling-in-react-16.html

[tlrobinson]

FYI I've moved the relevant parts of the previous branch to a new branch from master since it was too difficult to merge all the package changes.

[tlrobinson]

Superseded by #6756 #6757 #6758