[1] JSX
1. What is JSX?
const h1 = <h1>hello world</h1>;
Does this code belong in a JavaScript file, an HTML file, or somewhere else?
The answer is...a JavaScript file! Despite what it looks like, your code doesn't actually contain any HTML at all.
The part that looks like HTML, <h1>Hello world</h1>, is something called JSX.
JSX is a syntax extension for JavaScript. It was written to be used with React. JSX code looks a lot like HTML.
What does "syntax extension" mean?
In this case, it means that JSX is not valid JavaScript. Web browsers can't read it!
If a JavaScript file contains JSX code, then that file will have to be compiled. That means that before the file reaches a web browser, a JSX compiler will translate any JSX into regular JavaScript.
2. JSX Elements
<h1>Hello world</h1>
A basic unit of JSX is called a JSX element.
This JSX element looks exactly like HTML! The only noticeable difference is that you would find it in a JavaScript file, instead of in an HTML file.
JSX elements are treated as JavaScript expressions. They can go anywhere that JavaScript expressions can go.
That means that a JSX element can be saved in a variable, passed to a function, stored in an object or array...you name it.
Here's an example of a JSX element being saved in a variable:
const navBar = <nav>I am a nav bar</nav>;
Here's an example of several JSX elements being stored in an object:
const myTeam = {
center: <li>Benzo Walli</li>,
powerForward: <li>Rasha Loa</li>,
smallForward: <li>Tayshaun Dasmoto</li>,
shootingGuard: <li>Colmar Cumberbatch</li>,
pointGuard: <li>Femi Billon</li>
};
3. Attributes In JSX
JSX elements can have attributes, just like HTML elements can.
A JSX attribute is written using HTML-like syntax: a name, followed by an equals sign, followed by a value. The value should be wrapped in quotes, like this:
my-attribute-name="my-attribute-value"
Here are some JSX elements with attributes:
<a href="http://www.example.com">Welcome to the Web</a>;
const title = <h1 id="title">Introduction to React.js: Part I</h1>;
A single JSX element can have many attributes, just like in HTML:
const panda = <img src="images/panda.jpg" alt="panda" width="500px" height="300px" />;
4. Nested JSX
You can nest JSX elements inside of other JSX elements, just like in HTML. Here's an example of a JSX <h1> element, nested inside of a JSX <a> element:
<a href="https://www.example.com"><h1>Click me!</h1></a>
To make this more readable, you can use HTML-style line breaks and indentation:
<a href="https://www.example.com">
<h1>
Click me!
</h1>
</a>
If a JSX expression takes up more than one line, then you must wrap the multi-line JSX expression in parentheses. This looks strange at first, but you get used to it:
(
<a href="https://www.example.com">
<h1>
Click me!
</h1>
</a>
)
Nested JSX expressions can be saved as variables, passed to functions, etc., just like non-nested JSX expressions can! Here's an example of a nested JSX expression being saved as a variable:
const theExample = (
<a href="https://www.example.com">
<h1>
Click me!
</h1>
</a>
);
5. JSX Outer Elements
There's a rule that we haven't mentioned: a JSX expression must have exactly one outermost element.
In other words, this code will work:
const paragraphs = (
<div id="i-am-the-outermost-element">
<p>I am a paragraph.</p>
<p>I, too, am a paragraph.</p>
</div>
);
But this code will not work:
const paragraphs = (
<p>I am a paragraph.</p>
<p>I, too, am a paragraph.</p>
);
The first opening tag and the final closing tag of a JSX expression must belong to the same JSX element! It's easy to forget about this rule, and end up with errors that are tough to diagnose. If you notice that a JSX expression has multiple outer elements, the solution is usually simple: wrap the JSX expression in a <div></div>.
6. Rendering JSX
You've learned how to write JSX elements! Now it's time to learn how to render them.
To render a JSX expression means to make it appear onscreen.
The following code will render a JSX expression:
ReactDOM.render(<h1>Hello world</h1>, document.getElementById('app'));
JavaScript is case-sensitive, so make sure to capitalize ReactDOM correctly!
import React from 'react';
import ReactDOM from 'react-dom';
// code here:
ReactDOM.render(<h1>Hello world</h1>, document.getElementById('app'));
7. ReactDOM.render() I
Let's examine the code that you just wrote.
You can see something called ReactDOM. What's that?
ReactDOM is the name of a JavaScript library. This library contains several React-specific methods, all of which deal with the DOM in some way or another.
We'll talk more later about how ReactDOM got into your file. For now, just understand that it's yours to use.
ReactDOM.render() is the most common way to render JSX. It takes a JSX expression, creates a corresponding tree of DOM nodes, and adds that tree to the DOM. That is the way to make a JSX expression appear onscreen.
import React from 'react';
import ReactDOM from 'react-dom';
ReactDOM.render(<h1>Hello world</h1>, document.getElementById('app'));
<h1>Hello world</h1> is the first argument being passed to ReactDOM.render(). ReactDOM.render()'s first argument should be a JSX expression, and it will be rendered to the screen.
8. ReactDOM.render() II
document.getElementById('app')
You just learned that ReactDOM.render() makes its first argument appear onscreen. But where on the screen should that first argument appear?
The first argument is appended to whatever element is selected by the second argument.
<!-- html file -->
<body>
<main id="app"></main>
</body>
See your html file. You can find an element that would be selected by document.getElementById('app').
That element acted as a container for ReactDOM.render()'s first argument! At the end of the previous exercise, this appeared on the screen:
9. Passing a Variable to ReactDOM.render()
ReactDOM.render()'s first argument should evaluate to a JSX expression, it doesn't have to literally be a JSX expression.
The first argument could also be a variable, so long as that variable evaluates to a JSX expression.
In this example, we save a JSX expression as a variable named toDoList. We then pass toDoList as the first argument to ReactDOM.render():
const toDoList = (
<ol>
<li>Learn React </li>
<li>Become a Developer </li>
</ol>
);
ReactDOM.render(
toDoList,
document.getElementById('app')
);
10. The Virtual DOM
One special thing about ReactDOM.render() is that it only updates DOM elements that have changed.
That means that if you render the exact same thing twice in a row, the second render will do nothing:
const hello = <h1>Hello world</h1>;
// This will add "Hello world" to the screen:
ReactDOM.render(hello, document.getElementById('app'));
// This won't do anything at all:
ReactDOM.render(hello, document.getElementById('app'));
This is significant! Only updating the necessary DOM elements is a large part of what makes React so successful.
11. class vs className
Grammar in JSX is mostly the same as in HTML, but there are subtle differences to watch out for. Probably the most frequent of these involves the word class.
In HTML, it's common to use class as an attribute name:
<h1 class="big">Hey</h1>
In JSX, you can't use the word class! You have to use className instead:
<h1 className="big">Hey</h1>
This is because JSX gets translated into JavaScript, and class is a reserved word in JavaScript.
When JSX is rendered, JSX className attributes are automatically rendered as class attributes.
12. Self-Closing Tags
Another JSX 'gotcha' involves self-closing tags.
What's a self-closing tag?
Most HTML elements use two tags: an opening tag (<div>), and a closing tag (</div>). However, some HTML elements such as <img> and <input> use only one tag. The tag that belongs to a single-tag element isn't an opening tag nor a closing tag; it's a self-closing tag.
When you write a self-closing tag in HTML, it is optional to include a forward-slash immediately before the final angle-bracket:
<!-- Fine in HTML with a slash: -->
<br />
<!-- Also fine, without the slash: -->
<br>
But!
In JSX, you have to include the slash. If you write a self-closing tag in JSX and forget the slash, you will raise an error:
<!-- Fine in JSX: -->
<br />
<!-- NOT FINE AT ALL in JSX: -->
<br>
13. Curly Braces in JSX
So far, we've focused on writing JSX expressions. It's similar to writing bits of HTML, but inside of a JavaScript file.
Now we're going to add something new: regular JavaScript, written inside of a JSX expression, written inside of a JavaScript file.
Whoaaaa...
ReactDOM.render(
<h1>2 + 3</h1>,
document.getElementById('app')
);
What do you think will appear in the browser?
Instead of adding 2 and 3, it printed out "2 + 3" as a string of text. Why?
This happened because 2 + 3 is located in between <h1> and </h1> tags.
Any code in between the tags of a JSX element will be read as JSX, not as regular JavaScript! JSX doesn't add numbers - it reads them as text, just like HTML.
You need a way to write code that says, "Even though I am located in between JSX tags, treat me like ordinary JavaScript and not like JSX."
You can do this by wrapping your code in curly braces.
The curly braces themselves won't be treated as JSX nor as JavaScript. They are markers that signal the beginning and end of a JavaScript injection into JSX, similar to the quotation marks that signal the boundaries of a string.
14. Variables in JSX
When you inject JavaScript into JSX, that JavaScript is part of the same environment as the rest of the JavaScript in your file.
That means that you can access variables while inside of a JSX expression, even if those variables were declared on the outside.
// Declare a variable:
const name = 'nykim';
// Access your variable
// from inside of a JSX expression:
const greeting = <p>Hello, {name}!</p>;
When writing JSX, it's common to use variables
// Use a variable to set the `height` and `width` attributes:
const sideLength = "200px";
const panda = (
<img
src="images/panda.jpg"
alt="panda"
height={sideLength}
width={sideLength} />
);
Notice how in this example, the <img />'s attributes each get their own line. This can make your code more readable if you have a lot of attributes on one element.
Object properties are also often used to set attributes:
const pics = {
panda: "http://bit.ly/1Tqltv5",
owl: "http://bit.ly/1XGtkM3",
owlCat: "http://bit.ly/1Upbczi"
};
const panda = (
<img
src={pics.panda}
alt="Lazy Panda" />
);
const owl = (
<img
src={pics.owl}
alt="Unimpressed Owl" />
);
const owlCat = (
<img
src={pics.owlCat}
alt="Ghastly Abomination" />
);
15. Event Listeners in JSX
JSX elements can have event listeners, just like HTML elements can. Programming in React means constantly working with event listeners.
You create an event listener by giving a JSX element a special attribute. Here's an example:
<img onClick={myFunc}/>
An event listener attribute's name should be something like onClick or onMouseOver: the word on, plus the type of event that you're listening for. You can see a list of valid event names here.
An event listener attribute's value should be a function. The above example would only work if myFunc were a valid function that had been defined elsewhere:
function myFunc() {
alert('Make myFunc the pFunc... omg that was horrible i am so sorry');
}
<img onClick={myFunc} />
Note that in HTML, event listener names are written in all lowercase, such as onclick or onmouseover. In JSX, event listener names are written in camelCase, such as onClick or onMouseOver.
16. JSX Conditionals: If Statements That Don't Work
Here's a rule that you need to know: you can not inject an if statement into a JSX expression.
This code will break:
(
<h1>
{
if (purchase.complete) {
'Thank you for placing an order!'
}
}
</h1>
)
The reason why has to do with the way that JSX is compiled. You don't need to understand the mechanics of it for now, but if you're interested then you can learn more here.
What if you want a JSX expression to render, but only under certain circumstances? You can't inject an if statement. What can you do?
You have lots of options. In the next few lessons, we'll explore some simple ways to write conditionals (expressions that are only executed under certain conditions) in JSX.
17. JSX Conditionals: If Statements That Do Work
How can you write a conditional, if you can't inject an if statement into JSX?
Well, one option is to write an if statement, and not inject it into JSX.
let message;
if (user.age >= drinkingAge) {
message = (
<h1>
Hey, check out this alcoholic beverage!
</h1>
);
} else {
message = (
<h1>
Hey, check out these earrings I got at Claire's!
</h1>
);
}
ReactDOM.render(
message,
document.getElementById('app')
);
It works, because the words if and else are not injected in between JSX tags. The if statement is on the outside, and no JavaScript injection is necessary.
This is a common way to express conditionals in JSX.
18. JSX Conditionals: The Ternary Operator
There's a more compact way to write conditionals in JSX: the ternary operator.
The ternary operator works the same way in React as it does in regular JavaScript. However, it shows up in React surprisingly often.
Recall how it works: you write x ? y : z, where x, y, and z are all JavaScript expressions. When your code is executed, x is evaluated as either "truthy" or "falsy." If x is truthy, then the entire ternary operator returns y. If x is falsy, then the entire ternary operator returns z. Here's a nice explanation if you need a refresher.
Here's how you might use the ternary operator in a JSX expression:
const headline = (
<h1>
{ age >= drinkingAge ? 'Buy Drink' : 'Do Teen Stuff' }
</h1>
);
And a more complicated example:
function coinToss () {
return Math.random() < 0.5 ? 'heads' : 'tails';
}
const pics = {
kitty: '../images/kitty.jpg',
puppy: '../images/puppy.jpg',
};
const img = <img src={pics[coinToss() === 'heads' ? 'kitty' : 'puppy']} />;
ReactDOM.render(
img,
document.getElementById('app')
);
19. JSX Conditionals: &&
We're going to cover one final way of writing conditionals in React: the && operator.
Like the ternary operator, && is not React-specific, but it shows up in React surprisingly often.
In the last lesson, you wrote statements that would sometimes render a kitty and other times render a puppy. && would not have been the best choice for those lessons.
&& works best in conditionals that will sometimes do an action, but other times do nothing at all.
Here's an example:
const tasty = (
<ul>
<li>Applesauce</li>
{ !baby && <li>Pizza</li> }
{ age > 15 && <li>Brussels Sprouts</li> }
{ age > 20 && <li>Oysters</li> }
{ age > 25 && <li>Grappa</li> }
</ul>
);
20. .map in JSX
The array method .map() comes up often in React. It's good to get in the habit of using it alongside JSX.
If you want to create a list of JSX elements, then .map() is often your best bet. It can look odd at first:
const strings = ['Home', 'Shop', 'About Me'];
const listItems = strings.map(string => <li>{string}</li>);
<ul>{listItems}</ul>
In the above example, we start out with an array of strings. We call .map() on this array of strings, and the .map() call returns a new array of <li>s.
On the last line of the example, note that {listItems} will evaluate to an array, because it's the returned value of .map()! JSX <li>s don't have to be in an array like this, but they can be.
// This is fine in JSX, not in an explicit array:
<ul>
<li>item 1</li>
<li>item 2</li>
<li>item 3</li>
</ul>
// This is also fine!
const liArray = [
<li>item 1</li>
<li>item 2</li>
<li>item 3</li>
];
<ul>{liArray}</ul>
Here's another example:
const fruits = ['banana', 'orange', 'lemon'];
const fruitsList = fruits.map(myFruit => <li>{myFruit}</li>);
ReactDOM.render(
<ul>{fruitsList}</ul>,
document.getElementById('app')
);
21. Keys
When you make a list in JSX, sometimes your list will need to include something called keys:
<ul>
<li key="li-01">Example1</li>
<li key="li-02">Example2</li>
<li key="li-03">Example3</li>
</ul>
A key is a JSX attribute. The attribute's name is key. The attribute's value should be something unique, similar to an id attribute.
keys don't do anything that you can see! React uses them internally to keep track of lists. If you don't use keys when you're supposed to, React might accidentally scramble your list-items into the wrong order.
Not all lists need to have keys. A list needs keys if either of the following are true:
1. The list-items have memory from one render to the next. For instance, when a to-do list renders, each item must "remember" whether it was checked off. The items shouldn't get amnesia when they render.
2. A list's order might be shuffled. For instance, a list of search results might be shuffled from one render to the next.
If neither of these conditions are true, then you don't have to worry about keys. If you aren't sure then it never hurts to use them!
const fruitsList = fruits.map(myFruit => <li>{myFruit}</li>);
It's tme to give your <li><li> a key attribute. What should key's value be?
.map()is going to loop over your expressions, creating a new <li></li>with a new key attribute on each loop. You need every key to b unique! How can you get .map() to produce a unique key, each time it loops?
First, add an i parameter to .map()'s inner function, so that you can access each fruit's unique index:
const fruitsList = fruits.map((myFruit, i) => <li>{myFruit}</li>);
Now, you can get a unique key on each loop, by adding the following attribute to your <li></li>:
<li key={'fruit_' + i}></li>
22. React.createElement
You can write React code without using JSX at all!
The majority of React programmers do use JSX, and we will use it for the remainder of this tutorial, but you should understand that it is possible to write React code without it.
The following JSX expression:
const h1 = <h1>Hello world</h1>;
can be rewritten without JSX, like this:
const h1 = React.createElement(
"h1",
null,
"Hello world"
);
When a JSX element is compiled, the compiler transforms the JSX element into the method that you see above: React.createElement(). Every JSX element is secretly a call to React.createElement().
We won't go in-depth into how React.createElement() works, but you can start with the documentation if you'd like to learn more!