TextInput unable to take Text node as placeholder

Description

When attempting to use a Text node as a placeholder of TextInput, the app throws an error (see screenshot). This is contrary to what is indicated by the docs, which states that placeholder is of type Node.

Reproduction

Sample Code:

import React, { Component } from 'react'
import { TextInput, Text } from 'react-native'

class App extends Component {

  render() {
    const myText = (
      <Text style={{fontStyle:'italic', fontSize: 40}}>This is my placeholder</Text>
    );
    return (

        <TextInput
          placeholder={myText}
        />
    )
  }
}

export default (App)

For whatever reason, this problem presents itself when running via react-native run-<ios|android> but is not seen when editing in the tutorial docs.

Solution

To address this issue, TextInput should actually be able to support taking a placeholder of type Node and rendering it.

Additional Information

• React Native version: Seen on both 0.37.0 and 0.41.2
• Platform: both
• Operating System: MacOS

Screenshots

ios	android

[brentvatne]

It should not take a node. I was saying that it is possible that Facebook internally has an implementation that supports nodes for placeholders, but the OSS version only supports text.

[hramos]

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we’re automatically closing issues after a period of inactivity. Please do not take it personally!

If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

• Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
• If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
• Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.