Passing/Accessing props in stateless child component

When you write

const ChildComponent = ({ someProp }) => (   <div>      <h1>Child Component {someProp}</h1>   </div>)

From all the props that you are passing to the childComponent you are just destructuring to get only someProp. If the number of props that you want to use in ChildComponents are countable(few) amongst the total number of props that are available, destructuring is a good option as it provides better readability.

Suppose you want to access all the props in the child component then you need not use {} around the argument and then you can use it like props.someProp

const ChildComponent = (props) => (   <div>      <h1>Child Component {props.someProp}</h1>   </div>)

Are you looking for the ES6 named argument syntax (which is merely destructuring) ?

const ChildComponent = ({ propName }) => (    <div>     <h1>Child Component</h1> </div>)const ChildComponent = (props) => ( // without named arguments    <div>     <h1>Child Component</h1> </div>)

Optionally there is a second argument to your function depending of whether you specified a context for your component or not.

Perhaps it would be more helpful wityh a links to the docs. As stated in the first article about functional components. Whatever props passed on to the component is represented as an object passed as first argument to your functional component.

To go a little further, about the spread notation within jsx.

When you write in a component :

<Child prop1={value1} prop2={value2} />

What your component will receive is an plain object which looks like this :

{ prop1: value1, prop2: value2 }

(Note that it's not a Map, but an object with only strings as keys).

So when you're using the spread syntax with a JS object it is effectively a shortcut to this

const object = { key1: value1, key2: value2 }<Component {...object}/>

Is equivalent to

<Component key1={value1} key2={value2} />

And actually compiles to

return React.createElement(Component, object); // second arg is props

And you can of course have the second syntax, but be careful of the order. The more specific syntax (prop=value) must come last : the more specific instruction comes last.

If you do :

<Component key={value} {...props} />

It compiles to

React.createElement(Component, _extends({ key: value }, props));

If you do (what you probably should)

<Component {...props} key={value} />

It compiles to

React.createElement(Component, _extends(props, { key: value }));

Where extends is *Object.assign (or a polyfill if not present).

To go further I would really recommend taking some time to observe the output of Babel with their online editor. This is very interesting to understand how jsx works, and more generally how you can implement es6 syntax with ES5 tools.

const ParentComponent = (props) => (   <div>     <h1>Parent Component</h1>     <ChildComponent {...props} />   </div>);const ChildComponent = ({prop1, ...rest}) =>{  <div>    <h1>Child Component with prop1={prop1}</h1>    <GrandChildComponent {...rest} />  </div>}const GrandChildComponent = ({prop2, prop3})=> {  <div>    <h1>Grand Child Component with prop2={prop1} and prop3={prop3}</h1>  </div>}