{"componentChunkName":"component---src-templates-docs-js","path":"/docs/jsx-in-depth.html","result":{"data":{"markdownRemark":{"html":"

Fundamentally, JSX just provides syntactic sugar for the React.createElement(component, props, ...children) function. The JSX code:

\n
<MyButton color=\"blue\" shadowSize={2}>\n  Click Me\n</MyButton>
\n

compiles into:

\n
React.createElement(\n  MyButton,\n  {color: 'blue', shadowSize: 2},\n  'Click Me'\n)
\n

You can also use the self-closing form of the tag if there are no children. So:

\n
<div className=\"sidebar\" />
\n

compiles into:

\n
React.createElement(\n  'div',\n  {className: 'sidebar'}\n)
\n

If you want to test out how some specific JSX is converted into JavaScript, you can try out the online Babel compiler.

\n

Specifying The React Element Type

\n

The first part of a JSX tag determines the type of the React element.

\n

Capitalized types indicate that the JSX tag is referring to a React component. These tags get compiled into a direct reference to the named variable, so if you use the JSX <Foo /> expression, Foo must be in scope.

\n

React Must Be in Scope

\n

Since JSX compiles into calls to React.createElement, the React library must also always be in scope from your JSX code.

\n

For example, both of the imports are necessary in this code, even though React and CustomButton are not directly referenced from JavaScript:

\n
import React from 'react';import CustomButton from './CustomButton';\nfunction WarningButton() {\n  // return React.createElement(CustomButton, {color: 'red'}, null);  return <CustomButton color=\"red\" />;\n}
\n

If you don’t use a JavaScript bundler and loaded React from a <script> tag, it is already in scope as the React global.

\n

Using Dot Notation for JSX Type

\n

You can also refer to a React component using dot-notation from within JSX. This is convenient if you have a single module that exports many React components. For example, if MyComponents.DatePicker is a component, you can use it directly from JSX with:

\n
import React from 'react';\n\nconst MyComponents = {\n  DatePicker: function DatePicker(props) {\n    return <div>Imagine a {props.color} datepicker here.</div>;\n  }\n}\n\nfunction BlueDatePicker() {\n  return <MyComponents.DatePicker color=\"blue\" />;}
\n

User-Defined Components Must Be Capitalized

\n

When an element type starts with a lowercase letter, it refers to a built-in component like <div> or <span> and results in a string 'div' or 'span' passed to React.createElement. Types that start with a capital letter like <Foo /> compile to React.createElement(Foo) and correspond to a component defined or imported in your JavaScript file.

\n

We recommend naming components with a capital letter. If you do have a component that starts with a lowercase letter, assign it to a capitalized variable before using it in JSX.

\n

For example, this code will not run as expected:

\n
import React from 'react';\n\n// Wrong! This is a component and should have been capitalized:function hello(props) {  // Correct! This use of <div> is legitimate because div is a valid HTML tag:\n  return <div>Hello {props.toWhat}</div>;\n}\n\nfunction HelloWorld() {\n  // Wrong! React thinks <hello /> is an HTML tag because it's not capitalized:  return <hello toWhat=\"World\" />;}
\n

To fix this, we will rename hello to Hello and use <Hello /> when referring to it:

\n
import React from 'react';\n\n// Correct! This is a component and should be capitalized:function Hello(props) {  // Correct! This use of <div> is legitimate because div is a valid HTML tag:\n  return <div>Hello {props.toWhat}</div>;\n}\n\nfunction HelloWorld() {\n  // Correct! React knows <Hello /> is a component because it's capitalized.  return <Hello toWhat=\"World\" />;}
\n

Choosing the Type at Runtime

\n

You cannot use a general expression as the React element type. If you do want to use a general expression to indicate the type of the element, just assign it to a capitalized variable first. This often comes up when you want to render a different component based on a prop:

\n
import React from 'react';\nimport { PhotoStory, VideoStory } from './stories';\n\nconst components = {\n  photo: PhotoStory,\n  video: VideoStory\n};\n\nfunction Story(props) {\n  // Wrong! JSX type can't be an expression.  return <components[props.storyType] story={props.story} />;}
\n

To fix this, we will assign the type to a capitalized variable first:

\n
import React from 'react';\nimport { PhotoStory, VideoStory } from './stories';\n\nconst components = {\n  photo: PhotoStory,\n  video: VideoStory\n};\n\nfunction Story(props) {\n  // Correct! JSX type can be a capitalized variable.  const SpecificStory = components[props.storyType];  return <SpecificStory story={props.story} />;}
\n

Props in JSX

\n

There are several different ways to specify props in JSX.

\n

JavaScript Expressions as Props

\n

You can pass any JavaScript expression as a prop, by surrounding it with {}. For example, in this JSX:

\n
<MyComponent foo={1 + 2 + 3 + 4} />
\n

For MyComponent, the value of props.foo will be 10 because the expression 1 + 2 + 3 + 4 gets evaluated.

\n

if statements and for loops are not expressions in JavaScript, so they can’t be used in JSX directly. Instead, you can put these in the surrounding code. For example:

\n
function NumberDescriber(props) {\n  let description;\n  if (props.number % 2 == 0) {    description = <strong>even</strong>;  } else {    description = <i>odd</i>;  }  return <div>{props.number} is an {description} number</div>;\n}
\n

You can learn more about conditional rendering and loops in the corresponding sections.

\n

String Literals

\n

You can pass a string literal as a prop. These two JSX expressions are equivalent:

\n
<MyComponent message=\"hello world\" />\n\n<MyComponent message={'hello world'} />
\n

When you pass a string literal, its value is HTML-unescaped. So these two JSX expressions are equivalent:

\n
<MyComponent message=\"&lt;3\" />\n\n<MyComponent message={'<3'} />
\n

This behavior is usually not relevant. It’s only mentioned here for completeness.

\n

Props Default to “True”

\n

If you pass no value for a prop, it defaults to true. These two JSX expressions are equivalent:

\n
<MyTextBox autocomplete />\n\n<MyTextBox autocomplete={true} />
\n

In general, we don’t recommend not passing a value for a prop, because it can be confused with the ES6 object shorthand {foo} which is short for {foo: foo} rather than {foo: true}. This behavior is just there so that it matches the behavior of HTML.

\n

Spread Attributes

\n

If you already have props as an object, and you want to pass it in JSX, you can use ... as a “spread” operator to pass the whole props object. These two components are equivalent:

\n
function App1() {\n  return <Greeting firstName=\"Ben\" lastName=\"Hector\" />;\n}\n\nfunction App2() {\n  const props = {firstName: 'Ben', lastName: 'Hector'};\n  return <Greeting {...props} />;}
\n

You can also pick specific props that your component will consume while passing all other props using the spread operator.

\n
const Button = props => {\n  const { kind, ...other } = props;  const className = kind === \"primary\" ? \"PrimaryButton\" : \"SecondaryButton\";\n  return <button className={className} {...other} />;\n};\n\nconst App = () => {\n  return (\n    <div>\n      <Button kind=\"primary\" onClick={() => console.log(\"clicked!\")}>\n        Hello World!\n      </Button>\n    </div>\n  );\n};
\n

In the example above, the kind prop is safely consumed and is not passed on to the <button> element in the DOM.\nAll other props are passed via the ...other object making this component really flexible. You can see that it passes an onClick and children props.

\n

Spread attributes can be useful but they also make it easy to pass unnecessary props to components that don’t care about them or to pass invalid HTML attributes to the DOM. We recommend using this syntax sparingly.

\n

Children in JSX

\n

In JSX expressions that contain both an opening tag and a closing tag, the content between those tags is passed as a special prop: props.children. There are several different ways to pass children:

\n

String Literals

\n

You can put a string between the opening and closing tags and props.children will just be that string. This is useful for many of the built-in HTML elements. For example:

\n
<MyComponent>Hello world!</MyComponent>
\n

This is valid JSX, and props.children in MyComponent will simply be the string "Hello world!". HTML is unescaped, so you can generally write JSX just like you would write HTML in this way:

\n
<div>This is valid HTML &amp; JSX at the same time.</div>
\n

JSX removes whitespace at the beginning and ending of a line. It also removes blank lines. New lines adjacent to tags are removed; new lines that occur in the middle of string literals are condensed into a single space. So these all render to the same thing:

\n
<div>Hello World</div>\n\n<div>\n  Hello World\n</div>\n\n<div>\n  Hello\n  World\n</div>\n\n<div>\n\n  Hello World\n</div>
\n

JSX Children

\n

You can provide more JSX elements as the children. This is useful for displaying nested components:

\n
<MyContainer>\n  <MyFirstComponent />\n  <MySecondComponent />\n</MyContainer>
\n

You can mix together different types of children, so you can use string literals together with JSX children. This is another way in which JSX is like HTML, so that this is both valid JSX and valid HTML:

\n
<div>\n  Here is a list:\n  <ul>\n    <li>Item 1</li>\n    <li>Item 2</li>\n  </ul>\n</div>
\n

A React component can also return an array of elements:

\n
render() {\n  // No need to wrap list items in an extra element!\n  return [\n    // Don't forget the keys :)\n    <li key=\"A\">First item</li>,\n    <li key=\"B\">Second item</li>,\n    <li key=\"C\">Third item</li>,\n  ];\n}
\n

JavaScript Expressions as Children

\n

You can pass any JavaScript expression as children, by enclosing it within {}. For example, these expressions are equivalent:

\n
<MyComponent>foo</MyComponent>\n\n<MyComponent>{'foo'}</MyComponent>
\n

This is often useful for rendering a list of JSX expressions of arbitrary length. For example, this renders an HTML list:

\n
function Item(props) {\n  return <li>{props.message}</li>;}\n\nfunction TodoList() {\n  const todos = ['finish doc', 'submit pr', 'nag dan to review'];\n  return (\n    <ul>\n      {todos.map((message) => <Item key={message} message={message} />)}    </ul>\n  );\n}
\n

JavaScript expressions can be mixed with other types of children. This is often useful in lieu of string templates:

\n
function Hello(props) {\n  return <div>Hello {props.addressee}!</div>;}
\n

Functions as Children

\n

Normally, JavaScript expressions inserted in JSX will evaluate to a string, a React element, or a list of those things. However, props.children works just like any other prop in that it can pass any sort of data, not just the sorts that React knows how to render. For example, if you have a custom component, you could have it take a callback as props.children:

\n
// Calls the children callback numTimes to produce a repeated component\nfunction Repeat(props) {\n  let items = [];\n  for (let i = 0; i < props.numTimes; i++) {    items.push(props.children(i));\n  }\n  return <div>{items}</div>;\n}\n\nfunction ListOfTenThings() {\n  return (\n    <Repeat numTimes={10}>\n      {(index) => <div key={index}>This is item {index} in the list</div>}    </Repeat>\n  );\n}
\n

Children passed to a custom component can be anything, as long as that component transforms them into something React can understand before rendering. This usage is not common, but it works if you want to stretch what JSX is capable of.

\n

Booleans, Null, and Undefined Are Ignored

\n

false, null, undefined, and true are valid children. They simply don’t render. These JSX expressions will all render to the same thing:

\n
<div />\n\n<div></div>\n\n<div>{false}</div>\n\n<div>{null}</div>\n\n<div>{undefined}</div>\n\n<div>{true}</div>
\n

This can be useful to conditionally render React elements. This JSX renders the <Header /> component only if showHeader is true:

\n
<div>\n  {showHeader && <Header />}  <Content />\n</div>
\n

One caveat is that some “falsy” values, such as the 0 number, are still rendered by React. For example, this code will not behave as you might expect because 0 will be printed when props.messages is an empty array:

\n
<div>\n  {props.messages.length &&    <MessageList messages={props.messages} />\n  }\n</div>
\n

To fix this, make sure that the expression before && is always boolean:

\n
<div>\n  {props.messages.length > 0 &&    <MessageList messages={props.messages} />\n  }\n</div>
\n

Conversely, if you want a value like false, true, null, or undefined to appear in the output, you have to convert it to a string first:

\n
<div>\n  My JavaScript variable is {String(myVariable)}.</div>
","frontmatter":{"title":"JSX In Depth","next":null,"prev":null},"fields":{"path":"content/docs/jsx-in-depth.md","slug":"docs/jsx-in-depth.html"}}},"pageContext":{"slug":"docs/jsx-in-depth.html"}},"staticQueryHashes":[]}