Fix context not passed through from primary renderer

[michalochman]

This was unintentionally introduced with #72, where parentComponent was not passed via render method used in Stage component to updateContainer call.

The issue surfaces for example when rendering with react-dom and trying to use Provider from react-redux, and then trying to connect PixiJS-based components to Redux store. This won't work as store will not be available in context once ReactPixiFiber kicks in.

[codecov]

Codecov Report

Merging #84 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #84   +/-   ##
=======================================
  Coverage   95.63%   95.63%           
=======================================
  Files          11       11           
  Lines         229      229           
=======================================
  Hits          219      219           
  Misses         10       10

Impacted Files	Coverage Δ
src/Stage.js	100% <100%> (ø)	⬆️
src/render.js	100% <100%> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b824d4c...d7b9928. Read the comment docs.

[michalochman]

Turns out this only works with Legacy Context API. New Context API is not passed through different renderers, see facebook/react#12796 and facebook/react#14101

Workarounds:

• react-reconciler questions facebook/react#13006 (comment)
• Imperative wrappers can't access current context value in commit phase facebook/react#13336 (comment)
• Support class component static contextType attribute facebook/react#13728 (React 16.6+)

[0xdevalias]

This solution is also pointed out here: michalochman/react-pixi-fiber#93.

I'll close this issue now as it is not related to this lib but to React Context API.

In case anyone else stumbles here from Google/etc, react-pixi-fibre now lists this in it's 'caveats' section of the README:

• https://github.com/michalochman/react-pixi-fiber#react-context-api-limitations

This links to the following React issue:

• Imperative wrappers can't access current context value in commit phase facebook/react#13336

Which seems to have been closed by this PR:

• Support class component static contextType attribute facebook/react#13728

Which seems to have been included in the React 16.6.0 changelog in this PR:

• Add 16.6.0 changelog facebook/react#13927

---

I haven't looked any deeper into things that that yet, but at least in theory, I would expect that the React side of this bug/issue/weirdness should be fixed now. So it may 'just work'.

Originally posted by @0xdevalias in pixijs/pixi-react#77 (comment)