Pauan

@martynasma It should work the same in `amcharts3-react`, your init handler was just a bit wrong: ```js AmCharts.addInitHandler(function(chart) { if (chart["export"] == null) { chart["export"] = {}; } if (chart["export"].enabled...

@vaidsu I'm sorry for taking so long to get back to you about this. Inside of the `setInterval` you are using this code: ``` self.setState({ dataProvider: self.generateData() }); ``` However,...

I have been unable to reproduce this issue. I have tested [all of our examples](https://github.com/amcharts/amcharts3-react/tree/77e35633b25367536f6e65d14ee959e458c4341a/examples) with React 16 and they all work perfectly. Can you please show me the code...

@rickbyington Your first code example is invalid. Try this code instead: ```js let Thing = () => { return ( Test ) } export { Thing } ``` (Notice the...

I'm not able to reproduce this. Is this still an issue with `@amcharts/amcharts3-angular` version `1.2.1`?

@pranav-xx Could you please provide your code?

@yairEO You shouldn't call `validateNow` or `validateData` Instead, you should: 1. [Create some `state` for your component.](https://github.com/amcharts/amcharts3-react/blob/9b9c6ae0749bdb9bc741e55a3a68a8ff4001648f/examples/create-react-app/src/App.js#L32-L35) 2. [Use the state in the `render` method.](https://github.com/amcharts/amcharts3-react/blob/9b9c6ae0749bdb9bc741e55a3a68a8ff4001648f/examples/create-react-app/src/App.js#L125) 3. [Use `setState` to change...

@justinbleach Try moving the `dataSets` object inside the `createDefaultChart` method, and then change `populateInitialData` like this: ```typescript poplateInitialData() { this.AmCharts.updateChart(this.chart, () => { this.chart.dataSets[0].title = currDatasetTitle; this.chart.dataSets[0].dataProvider = this.deviceStatus; });...

@shivangkumar Thanks a lot for that! However, I don't think it's quite correct. Charts aren't required to have a `legend`, and if they don't have a `legend` then your code...

Try using `npm install && npm start` instead. Using `&` has very different behavior from `&&`