Rewrite readme mixin example to use Higher Order Component

[morenoh149]

Hello, I see the readme demonstrates how to build a form element. However it utilizes the mixins field.

Now that mixins are considered harmful would a rewrite of the example in the readme be welcome?

[aesopwolf]

Ah, yes! This has been on my todo list for a long time.

[Jareechang]

@aesopwolf and @morenoh149 any progressive with this ? If not, I could help with this!

[morenoh149]

@Jareechang I'd submit a quick PR and link here a gist. I'm sure 20 other folks would appreciate it even if the maintainers choose never to change the readme. Sadly I've lost the context I had when I opened this issue 😛

[Jareechang]

@morenoh149, ok. I'll go ahead and do that 😄.

up to date documentation / examples = ❤️ for developers!

[aesopwolf]

@Jareechang I haven't made an progress with this. I'll gladly accept a PR though!

[morenoh149]

With the announced changes in v16 this will become a more pressing topic https://facebook.github.io/react/blog/2017/04/07/react-v15.5.0.html

[Jareechang]

Sorry for being late on this one. I am currently updating the DOCS and examples with new syntax which hopefully would help! PR coming soon, stay tuned peeps!

[Jareechang]

if anyone is interested is still stuck on how to convert away from using mixins, see my PR at #449. It provides an example of this. Feel free to reach out to me if you are stuck.

[rkuykendall]

This issue has been SOLVED in the new formsy organization with Formsy 1.0.1: https://github.com/formsy/formsy-react