Support strings as children

[bclinkinbeard]

This adds support for translating the following schema into markup like <p>This paragraph has <a href="http://google.com">a link</a> inside it.</p>.

{
  component: 'p',
  children: [
    'This paragraph has ',
    {
      component: 'a',
      href: 'http://google.com',
      text: 'a link'
    },
    ' inside it'
  ]
}

It seems like this kind of thing should definitely be supported since React supports it as seen in this Babel REPL link.

The question it raises is what about the "special" text property? Should it be removed or should both formats be supported?

Happy to add tests and stuff if you want to accept this change.

[eiof]

This looks good. I think it'd make sense to move away from text, but for now we should support both. A strategy can be made for deprecating text, such as printing console warnings and having a planned release for dropping it.

Could you add tests? I can merge after that.

[bclinkinbeard]

Just a heads up that I don't think I'll be fleshing this out. Jasmine appears to swallow console.log statements in the code under test, which makes debugging super difficult.

[eiof]

@bclinkinbeard While I was working on a test, I had some thoughts. I understand your reasoning for wanting this feature, but the intention of react-json-schema is to accept JSON.

This library constructs React elements from JSON by mapping JSON definitions to React components that you expose.

It's less about being an alternative API for React's createElement. We chose to build our tool this way so we can feature schema validation.

I see you've already forked react-json-schema for your own use, which I think is for the best. I did get a test working around our planned 1.1.0 release integrated with this concept, in case you want to use that. You can fork it here: https://github.com/TechniqueSoftware/react-json-schema/tree/patch-1-a

I'm still open to ideas or suggestions, but for now I'm closing this issue.