June 22, 2020

1370 words 7 mins read

kentcdodds/bookshelf

kentcdodds/bookshelf

Build a ReactJS App workshop

repo name kentcdodds/bookshelf
repo link https://github.com/kentcdodds/bookshelf
homepage https://kentcdodds.com/workshops/build-react-apps
language JavaScript
size (curr.) 3236 kB
stars (curr.) 970
created 2019-05-10
license

Build a React App - Bookshelf

๐Ÿ‘‹ hi there! My name is Kent C. Dodds and this is the source material for Build a React App!

Travis Build Status AppVeyor Build Status GPL-3.0 License All Contributors PRs Welcome Code of Conduct

Pre-Workshop Instructions/Requirements

NOTE: This repository is used for a multi-part workshop

In order for us to maximize our efforts during the workshop, please complete the following things to prepare.

  • ๐Ÿ“บ only necessary if the workshop is remote via Zoom

  • ๐Ÿ‘‹ specific to the material for this workshop

  • 3๏ธโƒฃ Only needed to prepare for part 3 of this workshop

  • 4๏ธโƒฃ Only needed to prepare for part 4 of this workshop

  • ๐Ÿ‘‹ Setup the project (follow the setup instructions below) (~5 minutes)

  • ๐Ÿ“บ Install and setup Zoom on the computer you will be using (~5 minutes)

  • ๐Ÿ“บ Watch Use Zoom for KCD Workshops (~8 minutes).

  • Watch How to get the bookshelf app setup (~18 minutes). Please do NOT skip this step.

  • ๐Ÿ‘‹ Watch The Beginner’s Guide to React (available free on Egghead.io), or have the equivalent experience (147 minutes)

  • ๐Ÿ‘‹ Watch my talk Why React Hooks (35 minutes)

  • ๐Ÿ‘‹ Go through my Learn React Hooks Workshop, or have the equivalent basic experience of using hooks. You should be experienced with useState, useEffect, and useRef.

  • ๐Ÿ‘‹ 3๏ธโƒฃ Go through my Advanced React Hooks Workshop, or have the equivalent basic experience of using advanced hooks. You should be experienced with useContext, useReducer, useMemo, and useCallback.

  • ๐Ÿ‘‹ 4๏ธโƒฃ Go through my Testing React Apps Workshop, TestingJavaScript.com, or have the equivalent experience testing React components with Jest and React Testing Library.

The more prepared you are for the workshop, the better it will go for you.

System Requirements

All of these must be available in your PATH. To verify things are set up properly, you can run this:

git --version
node --version
npm --version

If you have trouble with any of these, learn more about the PATH environment variable and how to fix it here for windows or mac/linux.

Setup

After you’ve made sure to have the correct things (and versions) installed, you should be able to just run a few commands to get set up:

git clone https://github.com/kentcdodds/bookshelf.git
cd bookshelf
npm run setup --silent

If you get any errors, please read through them and see if you can find out what the problem is. If you can’t work it out on your own then please file an issue and provide all the output from the commands you ran (even if it’s a lot).

Running the app

To get the app up and running (and really see if it worked), run:

npm start

This should start up your browser. If you’re familiar, this is a standard react-scripts application.

You can also open the production deployment: bookshelf.lol.

Running the tests

npm test

This will start Jest in watch mode. Read the output and play around with it. The tests are there to help you reach the final version, however sometimes you can accomplish the task and the tests still fail if you implement things differently than I do in my solution, so don’t look to them as a complete authority.

Working through the exercises

To get started, run:

node go

This will allow you to choose which exercise you want to work on. From there, open the INSTRUCTIONS.md file and follow the instructions there.

If you’d like to work on an extra credit, but you want to skip the preceding steps, you can run node go again:

node go

This will let you choose the next exercise or you can choose which part of the exercise you’d like to work on. This will update your exercise files to the correct version for you to work on that extra credit.

Workshop Outline

Snuggle up next to the ๐Ÿ”ฅ with a good ๐Ÿ“š

๐Ÿ‘‹ I’m Kent C. Dodds

Schedule

This workshop is a bit different from my other workshops. The exercises are much longer and you’ll have more time to complete them. We’ll also be taking breaks mid-exercise, wherever there’s a need. So consider this schedule to be very loose.

Part 1

  • ๐Ÿ˜ด Logistics
  • ๐Ÿ’ช 01. Bootstrap
  • ๐Ÿ˜ด 10 Minutes
  • ๐Ÿ’ช 02. Styles
  • ๐ŸŒฎ 30 Minutes
  • ๐Ÿ’ช 03. Data Fetching
  • ๐Ÿ˜ด 10 Minutes
  • โ“ Q&A

Part 2

  • ๐Ÿ˜ด Logistics
  • ๐Ÿ’ช 04. Authentication
  • ๐Ÿ˜ด 10 Minutes
  • ๐Ÿ’ช 05. Routing
  • ๐ŸŒฎ 30 Minutes
  • ๐Ÿ’ช 06. Cache Management
  • โ“ Q&A

Part 3

  • ๐Ÿ˜ด Logistics
  • ๐Ÿ’ช 07. Context
  • ๐Ÿ˜ด 10 Minutes
  • ๐Ÿ’ช 08. Flexible Component
  • ๐ŸŒฎ 30 Minutes
  • ๐Ÿ’ช 09. Performance
  • ๐Ÿ˜ด 10 Minutes
  • ๐Ÿ’ช 10. Render as you fetch
  • โ“ Q&A

Part 4

  • ๐Ÿ˜ด Logistics
  • ๐Ÿ’ช 11. Unit Testing
  • ๐Ÿ˜ด 10 Minutes
  • ๐Ÿ’ช 12. Testing Hooks and Components
  • ๐ŸŒฎ 30 Minutes
  • ๐Ÿ’ช 13. Integration Testing
  • ๐Ÿ˜ด 10 Minutes
  • ๐Ÿ’ช 14. E2E Testing
  • โ“ Q&A

Questions

Please do ask! Interrupt me. If you have an unrelated question, please ask on my AMA.

Zoom (for remote workshops)

  • Help us make this more human by keeping your video on if possible
  • Keep microphone muted unless speaking
  • Breakout rooms

Exercises

The exercises are in different branches. Each branch changes the INSTRUCTIONS.md file to contain instructions you need to complete the exercise.

The purpose of the exercise is not for you to work through all the material. It’s intended to get your brain thinking about the right questions to ask me as I walk through the material.

Helpful Emoji ๐Ÿจ ๐Ÿ’ช ๐Ÿ ๐Ÿ’ฐ ๐Ÿ’ฏ ๐Ÿฆ‰ ๐Ÿ“œ ๐Ÿ’ฃ ๐Ÿ‘จโ€๐Ÿ’ผ ๐Ÿšจ

Each exercise has comments in it to help you get through the exercise. These fun emoji characters are here to help you.

  • Kody the Koala Bear ๐Ÿจ will tell you when there’s something specific you should do
  • Matthew the Muscle ๐Ÿ’ช will indicate what you’re working with an exercise
  • Chuck the Checkered Flag ๐Ÿ will indicate that you’re working with a final version
  • Marty the Money Bag ๐Ÿ’ฐ will give you specific tips (and sometimes code) along the way
  • Hannah the Hundred ๐Ÿ’ฏ will give you extra challenges you can do if you finish the exercises early.
  • Olivia the Owl ๐Ÿฆ‰ will give you useful tidbits/best practice notes and a link for elaboration and feedback.
  • Dominic the Document ๐Ÿ“œ will give you links to useful documentation
  • Berry the Bomb ๐Ÿ’ฃ will be hanging around anywhere you need to blow stuff up (delete code)
  • Peter the Product Manager ๐Ÿ‘จโ€๐Ÿ’ผ helps us know what our users want
  • Alfred the Alert ๐Ÿšจ will occasionally show up in the test failures with potential explanations for why the tests are failing.

Workflow

  • Checkout the exercise branch
  • Read through the INSTRUCTIONS.md
  • Start exercise
  • Go through every mentioned file and follow the instructions from the emoji
  • We all come back together
  • I go through the solution and answer questions
  • Move on to the next exercise.
  • Repeat.

App Data Model

  • User

    • id: string
    • username: string
  • List Item

    • id: string
    • bookId: string
    • ownerId: string
    • rating: number (-1 is no rating, otherwise it’s 1-5)
    • notes: string
    • startDate: number (Date.now())
    • finishDate: number (Date.now())

For convenience, our friendly backend engineers also return a book object on each list item which is the book it’s associated to. Thanks backend folks!

/me wishes we could use GraphQL

If your “database” gets out of whack, you can purge it via:

window.__bookshelf.purgeUsers()
window.__bookshelf.purgeListItems()
  • Book

    • id: string
    • title: string
    • author: string
    • coverImageUrl: string
    • pageCount: number
    • publisher: string
    • synopsis: string

Workshop Feedback

Each exercise has an Elaboration and Feedback link. Please fill that out after the exercise and instruction.

At the end of the workshop, please go to this URL to give overall feedback. Thank you!

Contributors

Thanks goes to these wonderful people (emoji key):

This project follows the all-contributors specification. Contributions of any kind welcome!

License

This material is available for private, non-commercial use under the GPL version 3. If you would like to use this material to conduct your own workshop, please contact me at me@kentcdodds.com

comments powered by Disqus