Support React Context

[theKashey]

No description provided.

[bbenezech]

In my app with 4.2.0, components nested in context Providers lose their state when hot reloading happens.
Is this expected atm? (-> basic support)

Thank you very much for the awesome support.

[theKashey]

Yeah, that was a basic update. Unfortunately, RHL does not contain any context related tests, as long enzyme still does not support them, as result some bugs exists.

So - the fix for your problem is almost ready - #983

[Cottin]

I get the above error when using Context. You've seen this before? Me doing something wrong?

[theKashey]

@Cottin - click on f and try to figure out that is it. This is not Context, just something with context.
And that "something" got required before hot-loader.

[NervosaX]

When making changes in my react component, inside a context provider, I get errors on this line:

56fdd05#diff-56f32a77d9820e3b9dc60ca87529a61cR341

saying that props is undefined on the child variable. Changing this to nextProps seems to solve the issue.

if (isContextProvider(child)) {
  extraContext = new Map(extraContext);
  extraContext.set(getContextProvider(child.type), child.nextProps.value);
  childName = 'ContextProvider';
}

[theKashey]

@NervosaX - changes are already in master. I need to fix #1001 and then will release a new version.
Unfortunately current version contain very nasty, almost buggy, behavior :(

[NervosaX]

@theKashey All good, I'll use my hack until then. Good luck!

[NervosaX]

Looks like 4.3.0 fixes this issue, can probably close this ticket now!

[theKashey]

👍