Use 'prop-types' package instead of React.PropTypes

[storybook-eol]

Use 'prop-types' package instead of React.PropTypes

[MichaelDeBoey]

@uppe-r react-treebeard uses also the deprecated React.PropTypes, like you can see in treebeard.js L36-L46, header.js L42-L49, node.js L100-L107 & decorators.js L97-L105

[nocategory]

@MichaelDeBoey You're right, only looked at the first files in the Warning.

[MichaelDeBoey]

@uppe-r I'll try to look at it (again) tonight, but I thought that the tests were failing me and I couldn't seem to pass them so... 😕

[MichaelDeBoey]

@uppe-r Tried my best in #67, but still get some errors 😕
Maybe you can help?

[MichaelDeBoey]

Oh sh*t I thought the test were failing for some other reason... 😕

So I guess I can just delete the test using reactid...

[nocategory]

Guess so @MichaelDeBoey . Doesn't make sense to keep something that isn't used anymore and just causes errors, right? 😆

[nocategory]

This error comes from velocity-react. It is fixed in v.1.3.0 by this pull request

[nocategory]

@MichaelDeBoey Hey! I can try. I'm kinda new, but from what I managed to find, with React v15 data-reactid is no longer used on every node (only server generated). As so, why are there still tests for reactid's?

[MichaelDeBoey]

@uppe-r That's strange 😕 Their test are still passing, but they shouldn't if it's no longer used since React v15.0 ... 😕

[nocategory]

@MichaelDeBoey The last PR's and non-PR's I see on Travis were using [email protected], like https://travis-ci.org/alexcurtis/react-treebeard/builds/197948568#L849

[MichaelDeBoey]

Should be fixed now 🙂

@alexcurtis Can you look at #67 please?

[MichaelDeBoey]

@uppe-r Do you know a way to increase coverage again?
Don't see what caused the decrease 😕

[nocategory]

@MichaelDeBoey No idea

[MichaelDeBoey]

v2.0.0is released as of now! 🙂