Splitting chart components into their own file about react-d3

[esbullington]

Yes, I'd like to start splitting the components into their own files. I should have some time this week to work on all this. Putting one major component per file is probably a good idea, just like you've done above.

In my own React projects, I've taken to using a single directory per major component (per major feature). They sometimes will contain a few subcomponents in them, and then the main component in a view.js file. I then put functions not directly tied to component logic in a controllers.js file. I then add an index.js file pointing to the view.js file, so I can import the component by its directory name (all this is using commonjs). I've been meaning to write a blog post about it, it works well for large scale projects in React.

We don't have to adopt that structure here, but I do like keeping my non-view-related logic out of the files that contain the components in larger projects. This approach also helps me keep the React state use to a minimum since none ofl the functions in the controllers.js file are state dependent -- all of these functions are pure.

I'd prefer to avoid the .react.js extension. If they're meant to indicate files containing jsx, I'd prefer to just use .jsx, since it seems more widely accepted (such as in Facebook's example projects).