Book Image

Learn React with TypeScript - Second Edition

By : Carl Rippon
4.4 (8)
Book Image

Learn React with TypeScript - Second Edition

4.4 (8)
By: Carl Rippon

Overview of this book

Reading, navigating, and debugging a large frontend codebase is a major issue faced by frontend developers. This book is designed to help web developers like you learn about ReactJS and TypeScript, both of which power large-scale apps for many organizations. This second edition of Learn React with TypeScript is updated, enhanced, and improved to cover new features of React 18 including hooks, state management libraries, and features of TypeScript 4. The book will enable you to create well-structured and reusable React components that are easy to read and maintain, leveraging modern design patterns. You’ll be able to ensure that all your components are type-safe, making the most of TypeScript features, including some advanced types. You’ll also learn how to manage complex states using Redux and how to interact with a GraphQL web API. Finally, you’ll discover how to write robust unit tests for React components using Jest. By the end of the book, you’ll be well-equipped to use both React and TypeScript.
Table of Contents (19 chapters)
1
Part 1: Introduction
6
Part 2: App Fundamentals
10
Part 3: Data
14
Part 4: Advanced React

Answers

Here are the answers to the questions on what you have learned in this chapter:

  1. The problem with the component definition is that its name is lowercase. React functions must be named with an uppercase first character:
    export function Important() {
      ...
    }
  2. The problem is that the name variable inside the div element isn’t enclosed in curly brackets. So, the word name will be output rather than the value of the name prop. Here’s the corrected version of the component:
    export function Name({ name }) {
      return <div>{name}</div>;
    }
  3. The problem is that a name prop is passed rather than firstName. Here’s the corrected JSX:
    <ContactDetails firstName="Fred" email="[email protected]" />
  4. The problem is that a click prop is passed rather than onClick. Here’s the corrected JSX:
    <button onClick={() => console.log("clicked")}>
      Click me
    </button>;
  5. The initial value of the loading state is true.
  6. The state isn’t updated using the state setter function. Here’s the corrected version of the state being set:
    export function Agree() {
      const [agree, setAgree] = useState();
      return (
        <button onClick={() => setAgree(true)}>
          Click to agree
        </button>
      );
    }
  7. The problem is that clicking the button will cause an error if onAgree isn’t passed because it will be undefined. Here’s the corrected version of the component:
    export function Agree({ onAgree }) {
      function handleClick() {
        if (onAgree) {
          onAgree();
        }
      }
      return (
        <button onClick={handleClick}>
          Click to agree
        </button>
      );
    }