Disclaimer: I own [NativeBase.io](http://nativebase.io/) and [Native Starter Pro](http://strapmobile.com/native-starter-pro/).

My team built Native Start Pro - [Premium React Native starter](http://strapmobile.com/native-starter-pro/) kit to quickly get off the ground on your next mobile app projects.

It includes

- Customizable variables just like Bootstrap
- Components like Contact list, Login screen, Simple forms, Slide-in menu, Inbox view, Compose Email, View Email

It also comes with a [detailed documentation](http://strapmobile.com/native-starter-pro-docs/docs.html).

-----
We Open-Sourced many components from [Native Starter Pro](http://strapmobile.com/native-starter-pro/) as [NativeBase.io](http://nativebase.io/) which is getting huge popularity on [ProductHunt](https://www.producthunt.com/tech/nativebase)

The closest thing is going to be material design https://github.com/xinthink/react-native-material-kit which is pretty great. At this time there is no bootstrap for react native, not to say that it isn&#39;t coming down the pipeline one day.

This project is aiming toward this direction:

https://github.com/react-native-community/react-native-elements

If you have protocol like so:

    protocol Messaging {
        func sendMessage(message: String)
    }

Is there any way to satisfy it in a class like so:

    class Messager: Messaging {
        func sendMessage(message: String, count: Int = 1) {}
    }

This would be nice to have, as the resulting signature of the protocol is satisfied by adding the defaulted parameter. Is there any way to get this to work with Swift 2?

This is a simplified example. Let&#39;s say, for the sake of argument, that the protocol is fixed. A solution can only update the Messager class. My goal is to be able to call `sendMessage()` like so:

    let m: Messaging = Messager()
    m.sendMessage(&quot;&quot;)

The only way I found to accomplish this (and satisfy the compiler) is with overloading like so:

    class Messager: Messaging {
        func sendMessage(message: String) {
            self.sendMessage(message, count: 1)
        }

        func sendMessage(message: String, count: Int = 1) {}
    }

The problem with this approach is that my defaults are then specified in two places and I lose the main advantage of Swift&#39;s default parameters.

Is it possible to satisfy Swift protocol and add defaulted arguments?

I just came across this concept of 

    var copy = Object.assign({}, originalObject);

which creates a copy of original object into the &quot;`copy`&quot; object. However, my question is, does this way of cloning object create a deep copy or a shallow copy? 

PS: The confusion is, if it creates a deep copy, then it would be the easiest way to clone an object.

JS: Does Object.assign() create deep copy or shallow copy

Ionic is awesome, but if you want to stay in the React-native world, I haven&#39;t found anything comparable and compatible. Let me know if you have any suggestions?

Is there any style framework for react-native similar to bootstrap for web?

<p>Ionic is awesome, but if you want to stay in the React-native world, I haven't found anything comparable and compatible. Let me know if you have any suggestions?</p>


According to the docs, [&quot;Without middleware, Redux store only supports synchronous data flow&quot;][1]. I don&#39;t understand why this is the case. Why can&#39;t the container component call the async API, and then `dispatch` the actions? 

For example, imagine a simple UI: a field and a button. When user pushes the button, the field gets populated with data from a remote server.

[![A field and a button][2]][2]

    import * as React from &#39;react&#39;;
    import * as Redux from &#39;redux&#39;;
    import { Provider, connect } from &#39;react-redux&#39;;

    const ActionTypes = {
        STARTED_UPDATING: &#39;STARTED_UPDATING&#39;,
        UPDATED: &#39;UPDATED&#39;
    };

    class AsyncApi {
        static getFieldValue() {
            const promise = new Promise((resolve) =&gt; {
                setTimeout(() =&gt; {
                    resolve(Math.floor(Math.random() * 100));
                }, 1000);
            });
            return promise;
        }
    }

    class App extends React.Component {
        render() {
            return (
                &lt;div&gt;
                    &lt;input value={this.props.field}/&gt;
                    &lt;button disabled={this.props.isWaiting} onClick={this.props.update}&gt;Fetch&lt;/button&gt;
                    {this.props.isWaiting &amp;&amp; &lt;div&gt;Waiting...&lt;/div&gt;}
                &lt;/div&gt;
            );
        }
    }
    App.propTypes = {
        dispatch: React.PropTypes.func,
        field: React.PropTypes.any,
        isWaiting: React.PropTypes.bool
    };

    const reducer = (state = { field: &#39;No data&#39;, isWaiting: false }, action) =&gt; {
        switch (action.type) {
            case ActionTypes.STARTED_UPDATING:
                return { ...state, isWaiting: true };
            case ActionTypes.UPDATED:
                return { ...state, isWaiting: false, field: action.payload };
            default:
                return state;
        }
    };
    const store = Redux.createStore(reducer);
    const ConnectedApp = connect(
        (state) =&gt; {
            return { ...state };
        },
        (dispatch) =&gt; {
            return {
                update: () =&gt; {
                    dispatch({
                        type: ActionTypes.STARTED_UPDATING
                    });
                    AsyncApi.getFieldValue()
                        .then(result =&gt; dispatch({
                            type: ActionTypes.UPDATED,
                            payload: result
                        }));
                }
            };
        })(App);
    export default class extends React.Component {
        render() {
            return &lt;Provider store={store}&gt;&lt;ConnectedApp/&gt;&lt;/Provider&gt;;
        }
    }



When the exported component is rendered, I can click the button and the input is updated correctly. 

Note the `update` function in the `connect` call. It dispatches an action that tells the App that it is updating, and then performs an async call. After the call finishes, the provided value is dispatched as a payload of another action.

What is wrong with this approach? Why would I want to use Redux Thunk or Redux Promise, as the documentation suggests?

**EDIT:** I searched the Redux repo for clues, and found that Action Creators were required to be pure functions in the past. For example, [here&#39;s a user trying to provide a better explanation for async data flow:][3]

&gt; The action creator itself is still a pure function, but the thunk function it returns doesn&#39;t need to be, and it can do our async calls

[Action creators are no longer required to be pure.][4] So, thunk/promise middleware was definitely required in the past, but it seems that this is no longer the case?


  [1]: http://redux.js.org/docs/advanced/AsyncFlow.html
  [2]: http://i.stack.imgur.com/GBI59.png
  [3]: https://github.com/reactjs/redux/issues/533
  [4]: https://github.com/reactjs/redux/issues/1088

Why do we need middleware for async flow in Redux?

I know that we can import all named modules with alias as below, 

    import * as name from &quot;module-name&quot;;

Ref: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import

Actually, I have re-exported my modules in A.js and the same is inherited in B.js. PFB. Now, it&#39;s two level of inheritance, so it&#39;s not a big deal to import the named modules. But, when I&#39;m taking this to 5 level of inheritance (A -&gt; B -&gt; C -&gt; D -&gt; E), I need to import all named modules in all files and need to do the (re)export the same in all. Instead of doing this, 

 - Is there any other way to copy scope of all named modules into all level without reiterating the wheel (Import and Export)
 - Behind the scene of this design is to make them to follow Opps concept and to avoid the redeclaration of the same modules.

**A.js** 

    import React from &#39;react&#39;;
    import I18n from &#39;i18n-js&#39;;
    import m1 from &#39;module1&#39;;
    import m2 from &#39;module2&#39;;

    export default class A extends React.Component {}

    export {React, I18n, m1, m2)

**B.js**

    import BaseComponent from &#39;./A&#39;;
    import {React, I18n, m1, m2) from &#39;./A;

    export default class B extends A {}

Is there any way to import all named modules without alias like `import {*} from &#39;./A&#39;` (instead of 2nd in B.js) 

es6 - import all named module without alias

I built an app with **ReactNative** both for iOS and android with a [`ListView`][1]. When populating the listview with a valid datasource, the following warning is printed at the bottom of the screen:

&gt; Warning: Each child in an array or iterator should have a unique &quot;key&quot;
&gt; prop. Check the render method of `ListView`.

What is the purpose of this warning? After the message they link to [this page](https://reactjs.org/docs/lists-and-keys.html#keys), where complete different things are discussed which have nothing to do with react native, but with web based reactjs.

My ListView is built with those statements:

    render() {
		var store = this.props.store;

        return (

            &lt;ListView
                dataSource={this.state.dataSource}
				renderHeader={this.renderHeader.bind(this)}
                renderRow={this.renderDetailItem.bind(this)}
				renderSeparator={this.renderSeparator.bind(this)}
                style={styles.listView}
                /&gt;

        );
    }

My DataSource consists of something like:

		var detailItems = [];

		detailItems.push( new DetailItem(&#39;plain&#39;, store.address) );
		detailItems.push( new DetailItem(&#39;map&#39;, &#39;&#39;) );

		if(store.telefon) {
			detailItems.push( new DetailItem(&#39;contact&#39;, store.telefon, &#39;Anrufen&#39;, &#39;fontawesome|phone&#39;) );
		}
		if(store.email) {
			detailItems.push( new DetailItem(&#39;contact&#39;, store.email, &#39;Email&#39;, &#39;fontawesome|envelope&#39;) );
		}
		detailItems.push( new DetailItem(&#39;moreInfo&#39;, &#39;&#39;) );

        this.setState({
            dataSource: this.state.dataSource.cloneWithRows(detailItems)
        });

And the ListView-Rows are rendered with stuff like:

			return (
				&lt;TouchableHighlight underlayColor=&#39;#dddddd&#39;&gt;
	                &lt;View style={styles.infoRow}&gt;
						&lt;Icon
						            name={item.icon}
						            size={30}
						            color=&#39;gray&#39;
						            style={styles.contactIcon}
						            /&gt;
						&lt;View style={{ flex: 1}}&gt;
							&lt;Text style={styles.headline}&gt;{item.headline}&lt;/Text&gt;
	                        &lt;Text style={styles.details}&gt;{item.text}&lt;/Text&gt;
						&lt;/View&gt;
                        &lt;View style={styles.separator}/&gt;
	                &lt;/View&gt;
	            &lt;/TouchableHighlight&gt;
	        );

Everything works fine and as expected, except the warning which seems to be complete nonsense to me.

Adding a key-property to my &quot;DetailItem&quot;-Class didn&#39;t solve the issue.

This is, what really will be passed to the ListView as a result of &quot;cloneWithRows&quot;:

    _dataBlob: 
    I/ReactNativeJS( 1293):    { s1: 
    I/ReactNativeJS( 1293):       [ { key: 2,
    I/ReactNativeJS( 1293):           type: &#39;plain&#39;,
    I/ReactNativeJS( 1293):           text: &#39;xxxxxxxxxx&#39;,
    I/ReactNativeJS( 1293):           headline: &#39;&#39;,
    I/ReactNativeJS( 1293):           icon: &#39;&#39; },
    I/ReactNativeJS( 1293):         { key: 3, type: &#39;map&#39;, text: &#39;&#39;, headline: &#39;&#39;, icon: &#39;&#39; },
    I/ReactNativeJS( 1293):         { key: 4,
    I/ReactNativeJS( 1293):           type: &#39;contact&#39;,
    I/ReactNativeJS( 1293):           text: &#39;(xxxx) yyyyyy&#39;,
    I/ReactNativeJS( 1293):           headline: &#39;Anrufen&#39;,
    I/ReactNativeJS( 1293):           icon: &#39;fontawesome|phone&#39; },
    I/ReactNativeJS( 1293):         { key: 5,
    I/ReactNativeJS( 1293):           type: &#39;contact&#39;,
    I/ReactNativeJS( 1293):           text: &#39;xxxxxxxxx@hotmail.com&#39;,
    I/ReactNativeJS( 1293):           headline: &#39;Email&#39;,
    I/ReactNativeJS( 1293):           icon: &#39;fontawesome|envelope&#39; },
    I/ReactNativeJS( 1293):         { key: 6, type: &#39;moreInfo&#39;, text: &#39;&#39;, headline: &#39;&#39;, icon: &#39;&#39; } ] },


As one key see, each record has a key property. The warning still exists.

  [1]: https://facebook.github.io/react-native/docs/listview.html#content

Warning: Each child in an array or iterator should have a unique &quot;key&quot; prop. Check the render method of `ListView`

I am building a small react app and my local images won&#39;t load. Images like `placehold.it/200x200` loads. I thought maybe it could be something with the server?

Here is my App.js

    
    import React, { Component } from &#39;react&#39;;
    
    class App extends Component {
    	render() {
    		return (
    			&lt;div className=&quot;home-container&quot;&gt;
    				&lt;div className=&quot;home-content&quot;&gt;
    					&lt;div className=&quot;home-text&quot;&gt;
    						&lt;h1&gt;foo&lt;/h1&gt;
    					&lt;/div&gt;
    					&lt;div className=&quot;home-arrow&quot;&gt;
    						&lt;p className=&quot;arrow-text&quot;&gt;
    							Vzděl&#225;n&#237;
    						&lt;/p&gt;
    						&lt;img src={&quot;/images/resto.png&quot;} /&gt;
    					&lt;/div&gt;
    				&lt;/div&gt;
    			&lt;/div&gt;
    		);
    	}
    }
    
    export default App;

index.js:

    import React, { Component } from &#39;react&#39;;
    import { render } from &#39;react-dom&#39;;
    import { Router, Route, Link } from &#39;react-router&#39;;
    import { createHistory } from &#39;history&#39;;
    import App from &#39;./components/app&#39;;
    
    let history = createHistory();
    
    render(
    	&lt;Router history={history} &gt;
    		&lt;Route path=&quot;/&quot; component={App} &gt;
    			&lt;Route path=&quot;vzdelani&quot; component=&quot;&quot; /&gt;
    			&lt;Route path=&quot;znalosti&quot; component=&quot;&quot; /&gt;
    			&lt;Route path=&quot;prace&quot; component=&quot;&quot; /&gt;
    			&lt;Route path=&quot;kontakt&quot; component=&quot;&quot; /&gt;
    		&lt;/Route&gt;
    		&lt;Route path=&quot;*&quot; component=&quot;&quot; /&gt;
    	&lt;/Router&gt;,
    	document.getElementById(&#39;app&#39;)
    );

and server.js:

    var path = require(&#39;path&#39;);
    var express = require(&#39;express&#39;);
    var webpack = require(&#39;webpack&#39;);
    var config = require(&#39;./webpack.config.dev&#39;);
    
    var app = express();
    var compiler = webpack(config);
    
    app.use(require(&#39;webpack-dev-middleware&#39;)(compiler, {
      noInfo: true,
      publicPath: config.output.publicPath
    }));
    
    app.use(require(&#39;webpack-hot-middleware&#39;)(compiler));
    
    app.get(&#39;*&#39;, function(req, res) {
      res.sendFile(path.join(__dirname, &#39;index.html&#39;));
    });
    
    app.listen(3000, &#39;localhost&#39;, function(err) {
      if (err) {
        console.log(err);
        return;
      }
    
      console.log(&#39;Listening at http://localhost:3000&#39;);
    });


  [1]: https://github.com/Baza58/react-app

React won&#39;t load local images

I know I&#39;m not supposed to mutate the input and should clone the object to mutate it. I was following the convention used on a redux starter project which used: 

    ADD_ITEM: (state, action) =&gt; ({
      ...state,
      items: [...state.items, action.payload.value],
      lastUpdated: action.payload.date
    })

for adding an item - I get the use of spread to append the item in the array.

for deleting I used: 

    DELETE_ITEM: (state, action) =&gt; ({
      ...state,
      items: [...state.items.splice(0, action.payload), ...state.items.splice(1)],
      lastUpdated: Date.now() 
    })

but this is mutating the input state object - is this forbidden even though I am returning a new object?

Is this the correct way to delete an item using redux?

I&#39;m trying to format a Date String in React Native.

Ex: 2016-01-04 10:34:23

Following is the code I&#39;m using.

    var date = new Date(&quot;2016-01-04 10:34:23&quot;);
    console.log(date);

My problem is, when I&#39;m emulating this on a iPhone 6S, it&#39;ll print Mon `Jan 04 2016 10:34:23 GMT+0530 (IST)` without any problem. But if I try with the iPhone 5S it prints nothing. And if you try to get the month by using a method like `date.getMonth()` it&#39;ll print `&quot;NaN&quot;`.

Why is this? What is the workaround?

Formatting a Date String in React Native

React Native doesn&#39;t support the CSS ```display``` property, and by default all elements use the behavior of ```display: flex``` (no ```inline-flex``` either). Most non-flex layouts can be simulated with flex properties, but I&#39;m flustered with inline text.

My app has a container that contains several words in text, some of which need formatting. This means I need to use spans to accomplish the formatting. In order to achieve wrapping of the spans, I can set the container to use ```flex-wrap: wrap```, but this will only allow wrapping at the end of a span rather than the traditional inline behavior of wrapping at word breaks.

The problem visualized (spans in yellow):

[![enter image description here][1]][1]

(via http://codepen.io/anon/pen/GoWmdm?editors=110)

Is there a way to get proper wrapping and true inline simulation using flex properties?





  [1]: http://i.stack.imgur.com/CgR94.png

Simulate display: inline in React Native

With the [forbid-prop-types](https://github.com/yannickcr/eslint-plugin-react/blob/master/docs/rules/forbid-prop-types.md) rule enabled, `eslint` forbids me from using `style: React.PropTypes.object`, and using `shape` is suggested.

But is it really necessary to define all the available properties there for this purpose like this?


    DEMO.propTypes = {
        style: React.PropTypes.shape({
            color: React.PropTypes.string,
            fontSize: React.PropTypes.number,
            ...
        })
    };

Too much definition code!

How to declare style in propTypes?

I have started to learn *React* out of curiosity and wanted to know the difference between React and React Native - though could not find a satisfactory answer using Google. React and React Native seems to have the same format. Do they have completely different syntax?


Content Type	Original Author	Original Content on Stackoverflow
Question	Mohamed El Mahallawy	View Question on Stackoverflow
Solution 1 - Reactjs	Sanket Sahu	View Answer on Stackoverflow
Solution 2 - Reactjs	Nader Dabit	View Answer on Stackoverflow
Solution 3 - Reactjs	giraffe_head	View Answer on Stackoverflow

Is there any style framework for react-native similar to bootstrap for web?

Reactjs Problem Overview

Reactjs Solutions

Solution 1 - Reactjs

Solution 2 - Reactjs

Solution 3 - Reactjs

JS: Does Object.assign() create deep copy or shallow copy

Is it possible to satisfy Swift protocol and add defaulted arguments?

Attributions