React PropTypes and CreateClass are deprecated about progress HOT 8 CLOSED

use ES6 with Babel would be better.

from progress.

No, just follow the convention, thanks.

from progress.

In the current project we use some es6 features without transpiling it into a production build, should we be doing that in the future?

Actually, when we run npm run pub, it will compile ES6 to ES5.

Mixins are no longer supported/recommended so I moved away from that, and was unsure whether it was necessary to use a HOC called Shape or something to reduce code duplication or just have the componentDidUpdate method in both Line and Circle.

How about an Inheritance Inversion HOC?

rc-tools complains about prop-types not being a dependency of the project when running the linter. Is there a way around this other than making it a dependency rather than a devDependency

prop-types should be dependencies, for rc-process supports React@<=15.4, and developers should not know prop-types if they use React@<=15.4

from progress.

@wemyss bravo 👍

from progress.

How about a PR @wemyss

from progress.

@benjycui starting work on this tomorrow 😸

from progress.

Thoughts on using flow over proptypes?

from progress.

That's what I did. I've made majority of the changes on my fork @ https://github.com/wemyss/progress but I have a few questions:

• In the current project we use some es6 features without transpiling it into a production build, should we be doing that in the future?
• Mixins are no longer supported/recommended so I moved away from that, and was unsure whether it was necessary to use a HOC called Shape or something to reduce code duplication or just have the componentDidUpdate method in both Line and Circle.
• rc-tools complains about prop-types not being a dependency of the project when running the linter. Is there a way around this other than making it a dependency rather than a devDependency

from progress.