Essential CSS
JavaScript Roadmap
Learn JavaScript
Mastering Web Typography
Practical Astro
Understanding Async JS
Unorthodox Tailwind
API Masterclass
Build and Deploy
The Beginner Freelancer
Real World Node
Profile Billing Logout
Learn JavaScript
Lesson Plan
  1. JavaScript and its ecosystem
    1. Welcome to Learn JavaScript!
    2. What is JavaScript used for?
    3. The JavaScript ecosystem
    4. Varying versions of JavaScript
  2. JS Basics
    1. Linking your JavaScript file
    2. Preparing your text editor
    3. The Console
    4. Comments
    5. On semicolons
    6. Strings, numbers and booleans
    7. Understanding Variables
    8. Understanding Functions
    9. The Flow of a Function
    10. Arrow functions
    11. Intro to objects
    12. If/else statements
    13. Comparing Objects
    14. The NOT operator
    15. Null and Undefined
    16. The BOM and the DOM
    17. Selecting an Element
    18. Changing Classes
    19. Listening to events
    20. Callbacks
  3. Building simple components
    1. How to think like a developer
    2. Starter files and Source codes
    3. Do this for every component
    4. ๐Ÿ›  Off-canvas menu: Building an off-canvas menu
    5. ๐Ÿ›  Modal: Building a Modal
    6. Lessons from the building process
    7. Debugging errors
    8. How to use a linter
  4. Arrays and loops
    1. Introduction to Arrays
    2. Array methods
    3. For loops
    4. The forEach loop
    5. Selecting multiple elements
    6. Nodes vs Elements
    7. ๐Ÿ›  Accordion: Building an accordion
  5. Dom basics
    1. Id, classes, attributes, and tags
    2. Changing CSS with JavaScript
    3. Getting CSS with JavaScript
    4. Changing Attributes
    5. Finding an element's size and position
    6. DOM Traversals
    7. ๐Ÿ›  Tabby: Building Tabby (A Tabbed component)
    8. ๐Ÿ›  Carousel: HTML and CSS
    9. ๐Ÿ›  Carousel: Switching slides with JavaScript
    10. ๐Ÿ›  Carousel: Working the dots
    11. ๐Ÿ›  Carousel: Positioning slides with JavaScript
  6. Events deep dive
    1. The listening element
    2. Default Behaviors
    3. Event propagation
    4. Event delegation
    5. Removing Event Listeners
    6. ๐Ÿ›  Modal: Closing the modal
    7. ๐Ÿ›  Accordion: Event delegation
    8. ๐Ÿ›  Tabby: Event delegation
    9. ๐Ÿ›  Carousel: Event delegation
  7. Transitions and Animations
    1. CSS Transitions
    2. CSS Animations
    3. Silky-smooth animations
    4. Integrating CSS transitions and animations with JavaScript
    5. Animating with JavaScript
    6. GreenSock Animation API (GSAP)
    7. ๐Ÿ›  Off-canvas menu: Animations
    8. ๐Ÿ›  Modal: Animating the modal
    9. ๐Ÿ›  Modal: Animating the pointing hand
    10. ๐Ÿ›  Modal: Animating the waving hand
    11. ๐Ÿ›  Modal: Wave hand animation with JavaScript (using GSAP)
    12. ๐Ÿ›  Accordion: Animations
    13. ๐Ÿ›  Carousel: Animations
  8. Useful JS features
    1. Ternary operators
    2. AND and OR operators
    3. Early returns
    4. Template Literals
    5. Destructuring
    6. Default parameters
    7. Enhanced Object Literals
    8. Rest and Spread
    9. Useful array methods
    10. Looping through objects
    11. Returning objects with implicit return
    12. ๐Ÿ›  Accordion: Using useful JavaScript features
    13. ๐Ÿ›  Tabby: Using useful JavaScript features
    14. ๐Ÿ›  Carousel: Useful JavaScript features
  9. JS Best practices
    1. Write declarative code
    2. Functions with a purpose
    3. Manage scope
    4. Reduce state changes
    5. Don't reassign
    6. Don't mutate
    7. Preventing Objects from mutating
    8. Preventing Arrays from mutating
    9. Write pure functions
    10. ๐Ÿ›  Accordion: Refactor
    11. ๐Ÿ›  Carousel: First refactor
    12. ๐Ÿ›  Carousel: Refactoring the dots part
    13. ๐Ÿ›  Carousel: Previous and next buttons
    14. ๐Ÿ›  Carousel: Second refactor
  10. Manipulating text and content
    1. Changing Text and HTML
    2. Creating HTML Elements
    3. Adding multiple elements to the DOM
    4. Removing Elements from the DOM
    5. ๐Ÿ›  Carousel: Creating dots with JavaScript
    6. ๐Ÿ› ๏ธ Calculator: HTML and CSS
    7. ๐Ÿ› ๏ธ Calculator: Happy Path
    8. ๐Ÿ› ๏ธ Calculator: Testing the Happy Path
    9. ๐Ÿ› ๏ธ Calculator: Easy Edge Cases
    10. ๐Ÿ› ๏ธ Calculator: Difficult Edge Cases
    11. ๐Ÿ› ๏ธ Calculator: Refactoring
    12. The switch statement
    13. ๐Ÿ› ๏ธ Calculator: Refactoring (Part 2)
    14. ๐Ÿ› ๏ธ Popover: Making one popover
    15. ๐Ÿ› ๏ธ Popover: Making four popovers
    16. ๐Ÿ› ๏ธ Popover: Making popovers with JavaScript
  11. Handling Forms
    1. Intro to forms
    2. Selecting form fields with JavaScript
    3. Form fields and their events
    4. Sanitize your output
    5. Generating unique IDs
    6. ๐Ÿ› ๏ธ Popover: Dynamic ID
    7. ๐Ÿ› ๏ธ Todolist: The HTML and CSS
    8. ๐Ÿ› ๏ธ Todolist: Creating tasks with JavaScript
    9. ๐Ÿ› ๏ธ Todolist: Deleting tasks with JavaScript
    10. ๐Ÿ› ๏ธ Typeahead: The HTML and CSS
    11. ๐Ÿ› ๏ธ Typeahead: Displaying predictions
    12. ๐Ÿ› ๏ธ Typeahead: Selecting a prediction
    13. ๐Ÿ› ๏ธ Typeahead: Bolding search terms
  12. Handling Dates
    1. The Date object
    2. Getting a formatted date
    3. Getting the time
    4. Local time and UTC Time
    5. Setting a specific date
    6. Setting a date with Date methods
    7. Adding (or subtracting) date and time
    8. Comparing Dates and times
    9. ๐Ÿ› ๏ธ Datepicker: HTML and CSS
    10. ๐Ÿ› ๏ธ Datepicker: Building the calendar
    11. ๐Ÿ› ๏ธ Datepicker: Building the datepicker with JavaScript
    12. ๐Ÿ› ๏ธ Datepicker: Previous and Next buttons
    13. ๐Ÿ› ๏ธ Datepicker: Selecting a date
    14. ๐Ÿ› ๏ธ Datepicker: Positioning the datepicker
    15. ๐Ÿ› ๏ธ Datepicker: Showing and hiding
    16. Formatting a date with toLocaleString
    17. setTimeout
    18. setInterval
    19. ๐Ÿ› ๏ธ Countdown timer: HTML and CSS
    20. ๐Ÿ› ๏ธ Countdown timer: JavaScript
    21. ๐Ÿ› ๏ธ Countdown timer: Counting Months
    22. ๐Ÿ› ๏ธ Countdown timer: Daylight Saving Time
    23. ๐Ÿ› ๏ธ Countdown timer: Counting Years
  13. Async JS
    1. Introduction to Ajax
    2. Understanding JSON
    3. The Fetch API
    4. Possible data types
    5. JavaScript Promises
    6. Requests and responses
    7. Sending a POST request
    8. Authentication
    9. Handling errors
    10. Viewing response headers
    11. CORS and JSONP
    12. XHR vs Fetch
    13. Using an Ajax library
    14. Reading API documentation
    15. Understanding curl
    16. ๐Ÿ› ๏ธ Todolist: The Todolist API
    17. ๐Ÿ› ๏ธ Todolist: Fetching tasks
    18. ๐Ÿ› ๏ธ Todolist: Creating tasks
    19. ๐Ÿ› ๏ธ Todolist: Editing tasks
    20. ๐Ÿ› ๏ธ Todolist: Deleting tasks
    21. ๐Ÿ› ๏ธ Todolist: Creating tasks with Optimistic UI
    22. ๐Ÿ› ๏ธ Todolist: Handling Optimistic UI errors
    23. ๐Ÿ› ๏ธ Todolist: Editing tasks with Optimistic UI
    24. ๐Ÿ› ๏ธ Todolist: Deleting tasks with Optimistic UI
    25. ๐Ÿ› ๏ธ Todolist: Refactor
    26. ๐Ÿ› ๏ธ Typeahead: How to add Ajax
    27. ๐Ÿ› ๏ธ Typeahead: Adding Ajax
    28. ๐Ÿ› ๏ธ Typeahead: Handling errors
    29. ๐Ÿ› ๏ธ Google Maps Clone: Creating your first Google Map
    30. ๐Ÿ› ๏ธ Google Maps Clone: Fetching JSONP via JavaScript
    31. ๐Ÿ› ๏ธ Google Maps Clone: Drawing directions
    32. ๐Ÿ› ๏ธ Google Maps Clone: Driving directions
    33. ๐Ÿ› ๏ธ Google Maps Clone: Handling errors
    34. ๐Ÿ› ๏ธ Google Maps Clone: Adding stopovers
    35. ๐Ÿ› ๏ธ Google Maps Clone: Refactor
  14. Advanced Async JS
    1. Requesting many resources at once
    2. Asynchronous functions
    3. Handling multiple awaits
    4. Asynchronous loops
    5. ๐Ÿ› ๏ธ Dota Heroes: Listing heroes
    6. ๐Ÿ› ๏ธ Dota Heroes: Filtering heroes (Part 1)
    7. ๐Ÿ› ๏ธ Dota Heroes: Filtering heroes (Part 2)
    8. ๐Ÿ› ๏ธ Dota Heroes: Refactoring
    9. ๐Ÿ› ๏ธ Dota Heroes: Hero Page
    10. ๐Ÿ› ๏ธ Dota Heroes: Making the hero page robust
    11. ๐Ÿ› ๏ธ Dota Heroes: Heroes page refactor
  15. Handling Keyboard Events
    1. Keyboard users
    2. Handling commonly used keys
    3. Keyboard events
    4. Understanding Tabindex
    5. Detecting the focused element
    6. Directing focus
    7. Preventing people from tabbing into elements
    8. How to choose keyboard shortcuts
    9. Creating single-key shortcuts
    10. ๐Ÿ› ๏ธ Off-canvas: Adding keyboard interaction
    11. ๐Ÿ› ๏ธ Modal: Adding keyboard interaction
    12. ๐Ÿ› ๏ธ Accordion: Adding keyboard interaction
    13. ๐Ÿ› ๏ธ Tabby: Adding keyboard interaction
    14. ๐Ÿ› ๏ธ Tabby: Refactoring
    15. ๐Ÿ› ๏ธ Carousel: Adding keyboard interaction
    16. ๐Ÿ› ๏ธ Carousel: Displaying help text
    17. ๐Ÿ› ๏ธ Calculator: Adding keyboard interaction
    18. ๐Ÿ› ๏ธ Popover: Keyboard
    19. ๐Ÿ› ๏ธ Popover: Refactor
    20. Keyboard shortcuts with Command and Control modifiers
    21. ๐Ÿ› ๏ธ Todolist: Keyboard
    22. ๐Ÿ› ๏ธ Typeahead: Keyboard
    23. ๐Ÿ› ๏ธ Typeahead: Selecting a prediction with the keyboard
    24. ๐Ÿ› ๏ธ Google Maps Clone: Keyboard
    25. ๐Ÿ› ๏ธ Dota Heroes: Keyboard
    26. ๐Ÿ› ๏ธ Datepicker: Tabbing in and out
    27. ๐Ÿ› ๏ธ Datepicker: Keyboard shortcuts
  16. Screen reader accessibility
    1. What is accessibility?
    2. How to use a screen reader
    3. Using NVDA
    4. Using Voiceover
    5. Aria roles
    6. Landmark roles
    7. Document structure roles
    8. Live region roles
    9. Widget roles
    10. Window and Abstract roles
    11. Accessible names and descriptions
    12. Hiding content
    13. ARIA properties and ARIA states
    14. ARIA for expandable widgets
    15. ๐Ÿ› ๏ธ Off-canvas: Accessibility
    16. ARIA for modal dialogs
    17. ๐Ÿ› ๏ธ Modal: Screen reader accessibility
    18. ๐Ÿ› ๏ธ Accordion: Screen reader accessibility
    19. ARIA for Tabbed components
    20. ๐Ÿ› ๏ธ Tabby: Screen reader accessibility
    21. ๐Ÿ› ๏ธ Tabby: Refactor
    22. ๐Ÿ› ๏ธ Carousel: Screen reader accessibility
    23. Roles that trigger Forms and Application modes
    24. What's next for accessibility?
  17. Handling Scroll
    1. The Scroll event
    2. ๐Ÿ› ๏ธ Auto-hiding Sticky-nav: HTML and CSS
    3. ๐Ÿ› ๏ธ Auto-hiding Sticky-nav: JavaScript
    4. ๐Ÿ› ๏ธ Auto-hiding Sticky-nav: Natural reveal
    5. Intersection Observer API
    6. Intersection Observer Options
    7. ๐Ÿ› ๏ธ Slide & Reveal
    8. ๐Ÿ› ๏ธ Slide & Reveal: Always fade-in when you scroll down
    9. ๐Ÿ› ๏ธ Slide & Reveal: Fine-tuning the animation
    10. ๐Ÿ› ๏ธ Infinite Scroll: Anatomy
    11. ๐Ÿ› ๏ธ Infinite Scroll: Infinite load
    12. ๐Ÿ› ๏ธ Infinite Scroll: Refactor
    13. ๐Ÿ› ๏ธ Infinite Scroll: Implementing the Infinite Scroll
  18. Mouse, Touch, and Pointer events
    1. Mouse Events
    2. ๐Ÿ› ๏ธ Spinning Pacman: HTML and CSS
    3. ๐Ÿ› ๏ธ Spinning Pacman: JavaScript
    4. Touch events
    5. Pointer events
    6. Touch-action
    7. ๐Ÿ› ๏ธ Spinning Pacman: Supporting Touch
    8. Cloning elements
    9. ๐Ÿ› ๏ธ DragDrop: HTML and CSS
    10. ๐Ÿ› ๏ธ DragDrop: JavaScript
    11. ๐Ÿ› ๏ธ DragDrop: Creating a drop preview
    12. ๐Ÿ› ๏ธ DragDrop: Sortable drop preview
    13. ๐Ÿ› ๏ธ DragDrop: Robustness
    14. ๐Ÿ› ๏ธ DragDrop: Refactor
  19. Object Oriented Programming
    1. Before we begin
    2. What is Object Oriented Programming?
    3. Four Flavours of Object Oriented Programming
    4. Inheritance
    5. This in JavaScript
    6. Call, bind, apply
    7. Creating Derivative Objects
    8. Composition vs Inheritance
    9. Polymorphism
    10. Encapsulation
    11. Closures
    12. Encapsulation in Object Oriented Programming
    13. Getters and Setters
    14. What OOP flavour to use
    15. When to use Object Oriented Programming
  20. Writing reusable code
    1. Creating reusable code by writing libraries
    2. Two Types of libraries
    3. Including libraries with Script tags
    4. Including libraries with ES6 Modules
    5. Dynamic imports
    6. ๐Ÿ› ๏ธ Off Canvas: Building a Library
    7. ๐Ÿ› ๏ธ Modal: Library setup
    8. ๐Ÿ› ๏ธ Modal: Opening the Modal
    9. ๐Ÿ› ๏ธ Modal: Closing the modal
    10. ๐Ÿ› ๏ธ Modal: Inheritance and Polymorphism
    11. ๐Ÿ› ๏ธ Modal: Resolving differences between subclasses
    12. ๐Ÿ› ๏ธ Modal: Exposing properties and methods
    13. ๐Ÿ› ๏ธ Accordion: Building a library
    14. ๐Ÿ› ๏ธ Tabby: Building a library
    15. ๐Ÿ› ๏ธ Carousel: Building a library
    16. ๐Ÿ› ๏ธ Calculator: Library
    17. ๐Ÿ› ๏ธ Calculator: Fixing the Clear Key
    18. ๐Ÿ› ๏ธ Calculator: Handling other keys
    19. ๐Ÿ› ๏ธ Calculator: State
    20. ๐Ÿ› ๏ธ Popover: Library
    21. ๐Ÿ› ๏ธ Popover: Adding event listeners
    22. ๐Ÿ› ๏ธ Typeahead: Library
    23. ๐Ÿ› ๏ธ DatePicker: Library
  21. Going from Vanilla JS to JS Frameworks
    1. ๐Ÿ› ๏ธ Building a Tiny framework
    2. ๐Ÿ› ๏ธ Tiny: Add event listeners
    3. ๐Ÿ› ๏ธ Tiny: Updating state
    4. ๐Ÿ› ๏ธ Tiny: Rendering Child Components
    5. ๐Ÿ› ๏ธ Tiny: Changing Parent State
    6. ๐Ÿ› ๏ธ Tiny: Passing Props
    7. ๐Ÿ› ๏ธ Tiny: Multiple Props
    8. ๐Ÿ› ๏ธ Tiny: Passing values from sibling components
    9. ๐Ÿ› ๏ธ Tiny: Mounting
    10. ๐Ÿ› ๏ธ Tiny: Passing props to descendants
    11. ๐Ÿ› ๏ธ Tiny: A tiny refactor
  22. Single Page Apps
    1. What is a Single Page App?
    2. Simple SPA using only CSS
    3. The Location Interface
    4. The History Interface
    5. Minimum viable server for a SPA
    6. ๐Ÿ› ๏ธ Dota SPA: Introduction
    7. ๐Ÿ› ๏ธ Dota SPA: Building The Heroes List
    8. ๐Ÿ› ๏ธ Dota SPA: Building the filters
    9. ๐Ÿ› ๏ธ Dota SPA: Filtering heroes
    10. ๐Ÿ› ๏ธ Dota SPA: Displaying filtered heroes
    11. ๐Ÿ› ๏ธ Dota SPA: Getting Ready to build the Hero Page
    12. ๐Ÿ› ๏ธ Dota SPA: Building the hero page
    13. ๐Ÿ› ๏ธ Dota SPA: Lore and abilities
    14. ๐Ÿ› ๏ธ Dota SPA: Routing for Single-page apps

๐Ÿ› ๏ธ Todolist: Deleting tasks with Optimistic UI

When we delete tasks the Optimistic UI way, we need to:

  1. Delete the task from the DOM
  2. Send a DELETE request to the server
  3. Handle the loading state
  4. Handle the loaded state
  5. Handle any errors that surface

Now, this sounds straightforward. But it isnโ€™t.

Letโ€™s walk through the steps and youโ€™ll see why.

Optimistic UI for deleting tasks: First try

Deleting a task from the DOM

When a user clicks on the delete icon, we want to remove the task from the DOM. This should be easy since youโ€™ve done it before.

taskList.addEventListener('click', event => {
if (!event.target.matches('.task__delete-button')) return
const taskElement = event.target.parentElement
taskList.removeChild(taskElement)
// Triggers empty state
if (taskList.children.length === 0) taskList.innerHTML = ''
})

Send a delete request

To send a DELETE request, we need to know the taskโ€™s id. We can find the taskโ€™s id from its checkbox.

taskList.addEventListener('click', event => {
// ...
const checkbox = taskElement.querySelector('input[type="checkbox"]')
const id = checkbox.id
})

Once we have the id, we can send a DELETE request.

taskList.addEventListener('click', event => {
// ...
zlFetch
.delete(`${rootendpoint}/tasks/${id}`, { auth })
.then(response => console.log(response))
.catch(error => console.log(error))
})

Handle the loading state

When we added a task, we used a spinner to tell users weโ€™re adding their task to the database.

When we delete tasks, we donโ€™t need a loading state because users wonโ€™t interact with the task anymore. This means we donโ€™t need to do anything for the loading state.

Handle the loaded state

We need to remove the deleted task from state.tasks.

First, we need to find the location of the task in state.tasks. We can find this location with findIndex.

taskList.addEventListener('click', event => {
// ...
zlFetch
.delete(`${rootendpoint}/tasks/${id}`, { auth })
.then(response => {
const index = state.tasks.findIndex(t => t.id === id)
})
.catch(error => console.log(error))
})

Then, we remove the task from state.tasks by using a combination of spread operators and slice. (Read this lesson again if this step sounds confusing).

taskList.addEventListener('click', event => {
// ...
zlFetch
.delete(`${rootendpoint}/tasks/${id}`, { auth })
.then(response => {
const index = state.tasks.findIndex(t => t.id === id)
state.tasks = [
...state.tasks.slice(0, index),
...state.tasks.slice(index + 1),
]
})
.catch(error => console.log(error))
})

Handling errors

If an error occurs, we need to:

  1. Create an error message
  2. Restore the task back to the DOM

Itโ€™s easy to create an error message. You already know what to do.

taskList.addEventListener('click', event => {
// ...
zlFetch.delete(/*...*/).catch(error => {
let errorMessage = ''
const { message } = error.body
if (message === 'TypeError: Failed to fetch') {
errorMessage = 'Failed to reach server. Please try again later.'
} else if (message === 'Unauthorized') {
errorMessage =
'Invalid username or password. Please check your username or password.'
} else {
errorMessage = error.body.message
}
const errorElement = makeErrorElement(errorMessage)
flashContainer.appendChild(errorElement)
})
})

We also need to restore the task back to the DOM. Here, we want to restore the task back to its original location.

If the user deletes one item at a time, restoring the task back to its original location is easy. We can use insertBefore to insert the task back to the original location.

To use insertBefore, you need to know the next task. To get the next task, you can use nextElementSibling.

If the deleted task is the last task, we need to use appendChild instead.

taskList.addEventListener('click', event => {
// ...
const nextTaskElement = taskElement.nextElementSibling
zlFetch.delete(/*...*/).catch(error => {
// ...
if (nextTaskElement) {
taskList.insertBefore(taskElement, nextTaskElement)
} else {
taskList.appendChild(taskElement)
}
})
})
Deletes a task. Shows error. Task returned to original position.

Unfortunately, things go haywire if users delete more than one task at a time. We wonโ€™t be able to put the deleted task back to where it belongs.

(I disabled error messages for the gif below).

Unable to restore the original task positions

We need to use another method.

Optimistic UI for deleting tasks: Second try

Hereโ€™s a possible method:

  1. We hide the task when user clicks the delete button.
  2. Then, we send a DELETE request to the server.
  3. If successful response: we delete task from DOM.
  4. If error response: we show the hidden task.

Hiding the task

To hide the task, we can use the hidden attribute.

taskList.addEventListener('click', event => {
// ...
const taskElement = event.target.parentElement
taskElement.setAttribute('hidden', true)
})

Sending the delete request

Next, we get the taskโ€™s id to send a DELETE request.

taskList.addEventListener('click', event => {
// ...
const checkbox = taskElement.querySelector('input[type="checkbox"]')
const id = checkbox.id
zlFetch
.delete(`${rootendpoint}/tasks/${id}`, { auth })
.then(response => console.log(response))
.catch(error => console.log(error))
})

Handling a successful response

When we receive a successful response, we delete the task.

taskList.addEventListener('click', event => {
// ...
zlFetch
.delete(/*...*/)
.then(response => {
// Deletes task
taskList.removeChild(taskElement)
})
.catch(error => console.log(error))
})

We also update state.tasks.

taskList.addEventListener('click', event => {
// ...
zlFetch
.delete(/*...*/)
.then(response => {
// ...
// Update state.tasks
const index = state.tasks.findIndex(t => t.id === id)
state.tasks = [
...state.tasks.slice(0, index),
...state.tasks.slice(index + 1),
]
})
.catch(error => console.log(error))
})

Handling errors

If we get an error, we show the task by removing the hidden attribute.

taskList.addEventListener('click', event => {
// ...
zlFetch
.delete(/*...*/)
.then(/*...*/)
.catch(error => {
// Show the task
taskElement.removeAttribute('hidden')
})
})

We also create an error message.

taskList.addEventListener('click', event => {
// ...
zlFetch
.delete(/*...*/)
.then(/*...*/)
.catch(error => {
// ...
taskElement.removeAttribute('hidden')
// Create error message
let errorMessage = ''
const { message } = error.body
if (message === 'TypeError: Failed to fetch') {
errorMessage = 'Failed to reach server. Please try again later.'
} else if (message === 'Unauthorized') {
errorMessage =
'Invalid username or password. Please check your username or password.'
} else {
errorMessage = error.body.message
}
const errorElement = makeErrorElement(errorMessage)
flashContainer.appendChild(errorElement)
})
})

You can delete tasks in any order now. The deleted tasks will always go back to their rightful positions if an error occurs.

(I removed the error messages in the gif below).

Tasks go back to their rightful positions.

Fixing the empty state

The empty state shows up if taskList contains 0 children elements. It doesnโ€™t show up if taskList contains children elements (even if theyโ€™re hidden).

Empty state doesnโ€™t show when tasks are hidden

We need it to show up if all children elements in taskList are hidden. The easiest way is to add an is-empty class to taskList.

We can use every to check if all tasks contain the hidden attribute.

every loops through an array of items. For each iteration, it checks if the callback is truthy. If the callback is truthy, it continues to the next iteration. If all iterations are truthy, every returns true. Otherwise, it returns false.

// Every example
function biggerThanTen(item) {
return item > 10
}
const array1 = [15, 20, 25].every(biggerThanTen)
console.log(array1) // true
const array2 = [5, 10, 15].every(biggerThanTen)
console.log(array2) // false

We can use every like this:

taskList.addEventListener('click', event => {
// ...
const allTasksAreHidden = [...taskList.children].every(element => {
return element.hasAttribute('hidden')
})
// ...
})

If all tasks are hidden, we add the is-empty class. Otherwise, we remove it.

taskList.addEventListener('click', event => {
// ...
if (allTasksAreHidden) {
taskList.classList.add('is-empty')
} else {
taskList.classList.remove('is-empty')
}
// ...
})

Weโ€™ll have to add this CSS for the code above to work.

.todolist__tasks.is-empty ~ .todolist__empty-state {
display: block;
}
Empty state shows when hiding tasks.

If the server returns an error, we need to hide the empty state. We can copy-paste the code we wrote above into the .catch method to do this.

taskList.addEventListener('click', event => {
// ...
zlFetch.delete(/*...*/)
.then(/*...*/)
.catch({
// ...
// Checks empty state
const allTasksAreHidden = [...taskList.children]
.every(element => {
return element.hasAttribute('hidden')
})
if (allTasksAreHidden) {
taskList.classList.add('is-empty')
} else {
taskList.classList.remove('is-empty')
}
})
})

Hiding the empty state when adding tasks

Try deleting all your tasks. This should trigger the empty state. Once you see the empty state, try adding a task. You should still see the empty state.

Delete all tasks. Create a task. Empty state still shows.

This happens because we left the is-empty class in the HTML after we deleted tasks.

The best way to hide the empty state when adding tasks is to remove the is-empty class.

todolist.addEventListener('submit', event => {
// ...
// Hides the empty state
taskList.classList.remove('is-empty')
zlFetch.post(/*...*/).then(/*...*/).catch(/*...*/)
})

If the server responds with an error, we need to show the empty state again. We donโ€™t have to do anything here because the :empty pseudo selector will take care of the rest.

Thatโ€™s it!