Cannot read property 'destroy' of undefined about react-jsx-highcharts HOT 7 CLOSED

Published as 1.3.2, thanks for the heads up and debugging.

from react-jsx-highcharts.

Hmm I'm not sure why the reference would be deleted. I've never seen that before.

What version of React are you using?

from react-jsx-highcharts.

I am not at work currently so I can't check, but since I upgraded our dependencies just few days ago it should be 15.6.1.

from react-jsx-highcharts.

Ok thanks, by any chance is the component mounted, then unmounted almost immediately? I can't think of many reasons why this.chart would be undefined.

from react-jsx-highcharts.

I didn't really spend a lot of time debugging, I just added an additional check so I can continue with development, but I can have a look if it helps.

from react-jsx-highcharts.

I found the cause of it. I have wrapped the chart in another component, that only renders its children when the status is not loading. It seems React instantiates the children before they are rendered, and then immediately unmounts them, before the this.chart object is created. If I take <HighGmsChart ... /> out of the StatusWrapper component, it works as expected. This is because isLoading and errorMessage are set from the Redux state, which causes a re-render almost instantly as the values change when the fetch request is sent.

<StatusWrapper
          isLoading={isAnalysisDataFetching}
          errorMessage={analysisDataError}
          <HighGmsChart height={450} seriesData={seriesData} />
</StatusWrapper>

Render method of StatusWrapper:

...
<div style={style}>
      {Spinner || ErrorMessage || children}
</div>

Although it is possible to handle this by react-jsx-highcharts users, I think this should be gracefully handled by the library. What do you think?

from react-jsx-highcharts.

Interesting, I didn't know about that React behaviour.

Yep I'll wrap the componentDidUnmount in an if statement and push out a new release.

from react-jsx-highcharts.