Fixed display of numeric data values
Added test for correct display of numeric data.
Try to stringify anything.
Combine if's.
(#71) Add tests for calling toString on data values

Add a test case for calling the toString() method on data values.
Add documentation for calling toString() on data values
Merge pull request #72 from glittershark/fix-numeric-display

Try to call `.toString()` on all passed data values (Thanks @joneshf and @zeroedin-bill)
Test case for #69

Test case for issue with column headers when rendering multiple tables
on a single page.
(#69) Fix issue with props getting polluted

Because `getDefaultProps` is cached once per component types, mutable
types like arrays and objects that are then modified by the components
were having their values shared across different components. This just
makes those values not set by getDefaultProps
Merge pull request #73 from glittershark/69/multiple-tables-per-page

Fix issue with props getting polluted by multiple components on the same page
Test case for additional issue with #69

Test case for the column headers in the *second* table polluting the
columns in the *first* instead of the other way around
Fix code style

Get rid of pointless comments and make braces same-line.
Test column headers in non-mounted DOM nodes

The pollution of HTML between the DOM nodes here wasn't actually
React's fault, instead it looks like it was caused by mounting the test
`<div>`s in the DOM. Doing it as non-mounted nodes fixes #69.
Merge pull request #74 from glittershark/69/fix-multiple-per-page-again

Test multiple tables in non-mounted DOM nodes
Don't call toString() on React component children

Don't call `toString()` on children of the <Td> if they're React
components

To check if a variable is a react component this just tests if
`typeof(thing.props) !== 'undefined'`, which is hacky and not very
robust, and a serious case for improvement.

Fixes #76
Merge pull request #77 from glittershark/76/custom-html-inside-td

Don't call toString() on React component children
Use dots reporter outside travis

Use the dots test reporter outside travis - the spec reporter was
getting pretty verbose.
Properly handle only one child Td in a Tr.

Because of React's (silliness)[1] with the type of children, checking
if the children was an array failed when there was only one child, so
data wasn't pulled from it.

This fixes #53

[1] http://facebook.github.io/react/docs/top-level-api.html#react.children
Merge pull request #79 from glittershark/53/tr-with-one-td

Properly handle only one child Td in a Tr.
Version 0.9.0