This switches to using the new context API (along with a peerDependency bump to React 16.6 in order to get support for the contextType field), and removes any use of deprecated methods. While removing componentWillReceiveProps calls, I eventually just had it generate the props to pass down during render instead of storing them in state as an intermediary, and used forceUpdate instead of setState calls when the backbone model had a change event. There were a few tests that were spying directly on the setState call, so I had to tweak those, but otherwise all of the functionality seems to be intact. The one thing that I'm not sure about is if this is going to cause any performance regressions, but it felt like it was ready for an initial review, at least.
This switches to using the new context API (along with a
peerDependencybump to React 16.6 in order to get support for thecontextTypefield), and removes any use of deprecated methods. While removingcomponentWillReceivePropscalls, I eventually just had it generate the props to pass down duringrenderinstead of storing them instateas an intermediary, and usedforceUpdateinstead ofsetStatecalls when the backbone model had a change event. There were a few tests that were spying directly on thesetStatecall, so I had to tweak those, but otherwise all of the functionality seems to be intact. The one thing that I'm not sure about is if this is going to cause any performance regressions, but it felt like it was ready for an initial review, at least.Resolves #23