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

🛠️ Google Maps Clone: Adding stopovers

Let’s say you want to travel to three places in Singapore. And you want to plot a route to all three places in the Google Maps clone.

The three places we’re going to use are:

  1. The Singapore Zoo
  2. Gardens by the bay
  3. Sentosa

To travel to three places, you use a feature in Google Maps called waypoints.

Waypoints

A waypoint is an intermediate point between the start and end of a journey. Using our three locations as an example, the points are:

  1. Startpoint: Singapore Zoo
  2. Waypoint: Gardens by the bay
  3. Endpoint: Sentosa

Google’s directions service lets you plot waypoints if you include a waypoints array. You can have up to 8 waypoints.

const request = {
origin: '...',
destination: '...',
waypoints: [
{
/*...*/
},
],
travelMode: 'DRIVING',
}

Each waypoint is an object that contains two properties:

  1. location: The address of the place
  2. stopover: This is a Boolean. If set to true, Google creates an intermediate point on the map. If set to false, Google plots a route that passes through this point.

The request we need to travel to the three places I mentioned is:

const request = {
origin: 'The Singapore Zoo',
destination: 'Sentosa',
waypoints: [
{
location: 'Gardens by the bay',
stopover: true,
},
],
travelMode: 'DRIVING',
}
// Draw the directions
getDirections(request).then(/*...*/).catch(/*...*/)
Three points on the map

Next, we want to add search boxes so users can search for directions with waypoints.

Adding search boxes

We want to let users decide whether they want to travel to more locations. To do this, we’ll add a <button> that says “Add new endpoint” in the search panel.

<div class="search-panel__body">
<!-- ... -->
<div class="search-panel__actions">
<!-- ... -->
<button type="button" class="secondary" data-js="add-searchbox">
+ Add new endpoint
</button>
</div>
</div>
Button for adding a new endpoint.

When a user clicks on “add new endpoint”, we want to add a search box to the search panel. To do this, we add an event listener to the “add new endpoint” button.

function initGoogleMap() {
// ...
const addSearchboxButton = searchPanel.querySelector(
'[data-js="add-searchbox"]',
)
addSearchboxButton.addEventListener('click', event => {
// ...
})
}

One way to add a search box is to write the HTML in JavaScript. You already know how to do this from the previous components, so we’re going to do something different.

We’re going to clone a search box since there are already two of them in the HTML.

To clone an element, we first need to find the element from the HTML. We can use any search box (but we’ll use the last one because it’s more convenient).

addSearchboxButton.addEventListener('click', event => {
const searchBoxes = [...searchPanel.querySelectorAll('.search-box')]
const lastSearchBox = searchBoxes[searchBoxes.length - 1]
})

We can clone an element with cloneNode. If we want to clone the entire element (with its contents), we need to pass true into cloneNode.

addSearchboxButton.addEventListener('click', event => {
// ...
const clone = lastSearchBox.cloneNode(true)
console.log(clone)
})

The cloned element has the same HTML as the original element.

The cloned element

We can add the cloned element into the DOM with insertAdjacentElement. insertAdjacentElement takes two arguments.

element.insertAdjacentElement(location, elementToInsert)

location can take four possible values:

  • beforebegin
  • afterbegin
  • beforeend
  • afterend
<!-- beforebegin -->
<p>
<!-- afterbegin -->
The quick brown fox jumps over the lazy dog
<!-- beforeend -->
</p>
<!-- afterend -->

This is how we can use insertAdjacentElement:

addSearchboxButton.addEventListener('click', event => {
// ...
lastSearchBox.insertAdjacentElement('afterend', clone)
})

(If we don’t use insertAdjacentElement, we need to use insertBefore, which takes more work).

The cloned element

Resetting the value

If the user wrote some text into the last search box before clicking “Add new endpoint”, the search box we add will contain that text.

Inserted search box has the same text as the previous search box

This happens because cloneNode(true) clones everything, even the value inside the input.

We need to reset any relevant details after cloning. In this case, we only need to reset the input value.

addSearchboxButton.addEventListener('click', event => {
// ...
const input = clone.querySelector('input')
input.value = ''
// ...
})
Inserted search box is now empty.

Adding Google Autocomplete

Our new search box doesn’t trigger Google’s Autocomplete.

Search box doesn’t trigger Google’s Autocomplete.

It doesn’t trigger Google’s Autocomplete because we have not initialised an Autocomplete with the new search box.

Let’s fix this by initializing the Autocomplete before we put the search box into the DOM.

addSearchboxButton.addEventListener('click', event => {
// ...
const input = clone.querySelector('input')
const autocomplete = new google.maps.places.Autocomplete(input)
autocomplete.bindTo('bounds', map)
lastSearchBox.insertAdjacentElement('afterend', clone)
})
Inserted search box triggers Google’s Autocomplete widget

Maximum number of search boxes

Google Maps lets you join up to 10 locations:

  1. 1 startpoint
  2. 8 waypoints
  3. 1 endpoint

We want to limit the number of search boxes so we don’t hit the WAYPOINT LIMIT EXCEEDED error. Here, we’ll limit search boxes to 10.

To do this, we stop the user from creating extra search boxes once there are 10 search boxes in the DOM.

addSearchboxButton.addEventListener('click', event => {
let searchBoxes = [...searchPanel.querySelectorAll('.search-box')]
if (searchBoxes.length >= 10) return
// ...
})

Deleting search boxes

Users may want to reduce the number of waypoints, so we need to give them a way to delete search boxes. To let them delete search boxes, we need to add a delete button to each search box.

<div class="search-box">
<span class="search-box__stopover-icon"></span>
<input type="search" placeholder="Starting point" />
<button hidden type="button" class="search-box__delete-icon">
<svg viewBox="0 0 20 20">
<use href="images/sprite.svg#delete"></use>
</svg>
</button>
</div>

We have two search boxes when the page loads. One for the origin, one for the destination. These search boxes are compulsory.

We don’t want to let users delete any search boxes when there are only two search boxes left, so we’ll add a hidden attribute to the delete buttons.

<div class="search-box">
<!-- ... -->
<button hidden ...>...</button>
</div>

Letting users delete search boxes

There are more than 2 search boxes once we add a search box. When this happens, we want to let users delete search boxes.

We can do this by removing the hidden attribute of all delete buttons.

Note: After adding a search box into the DOM, we have to use querySelectorAll again to get the search boxes (because the DOM has changed). querySelectorAll doesn’t update automatically.

// Adds new searchboxes
addSearchboxButton.addEventListener('click', event => {
let searchBoxes = [...searchPanel.querySelectorAll('.search-box')]
// ...
// Lets users delete search box.
searchBoxes = [...searchPanel.querySelectorAll('.search-box')]
searchBoxes.forEach(searchBox => {
const deleteButton = searchBox.querySelector('button')
deleteButton.removeAttribute('hidden')
})
})
Shows delete button when hovering over the search box.

To delete a search box, we remove the search box from the DOM. Here, we can add an event listener to the search panel. (Using the event delegation pattern).

searchPanel.addEventListener('click', event => {
// ...
})

First, we want to check if the user clicked a delete button. If they did not click a delete button, we bail from the function.

searchPanel.addEventListener('click', event => {
const deleteButton = event.target.closest('.search-box__delete-icon')
if (!deleteButton) return
})

To remove the search box, we need to find the search box. We can find it with parentElement. Then, we can delete the search box with removeChild.

searchPanel.addEventListener('click', event => {
// ...
const searchBox = deleteButton.parentElement
const searchBoxParent = searchBox.parentElement
searchBoxParent.removeChild(searchBox)
})
Deletes the third search box.

Deleting Google Autocomplete predictions

Each input element comes with their own Google Autocomplete predictions. As you can see in this GIF below, when you add a search box, the number of .pac-container increases by one.

Google Autocomplete creates a .pac-container div when you initialize the Autocomplete.
  • The first .pac-container is for the first search box
  • The second .pac-container is for the second search box
  • And so on

We can remove the .pac-container if we know the index of the search box.

searchPanel.addEventListener('click', event => {
// ...
const searchBox = deleteButton.parentElement
const searchBoxParent = searchBox.parentElement
const searchBoxes = [...searchPanel.querySelectorAll('.search-box')]
const index = searchBoxes.findIndex(sb => sb === searchBox)
const googleAutocomplete = document.querySelectorAll('.pac-container')[index]
searchBoxParent.removeChild(searchBox)
document.body.removeChild(googleAutocomplete)
// ...
})
Deletes the Google autocomplete that’s bound to the search box.

Correcting placeholders

If you delete the first search box, you’ll end up with two endpoints. This isn’t ideal.

Two search boxes with ‘Ending Point’ placeholders.

We always want the first search box to be “Starting Point”. And the last search box to be “Ending Point”. Here we have to use querySelectorAll to get the search boxes again since the DOM was changed.

searchBoxes = [...searchPanel.querySelectorAll('.search-box')]
searchBoxes[0].querySelector('input').placeholder = 'Starting point'
First search box always says ‘Starting Poing’.

If you want to, try making the middle search boxes say “Waypoints” as an exercise.

Ensuring there are two search boxes.

We need to have two search boxes for the Google Maps clone. We don’t want to let users delete search boxes if there are only two in the search panel.

We’ll hide the delete buttons if there are only two search boxes left.

searchPanel.addEventListener('click', event => {
// ...
if (searchBoxes.length <= 2) {
searchBoxes.forEach(searchBox => {
const deleteButton = searchBox.querySelector('button')
deleteButton.setAttribute('hidden', true)
})
}
})

Drawing the route

The UI work is done. What’s left is to:

  1. Get information from the search panel
  2. Change the information to what Google’s Directions Service needs
  3. Send the request

Here, we need to get the address from each search box. We’ll first get all the search boxes.

searchPanel.addEventListener('submit', event => {
event.preventDefault()
const searchBoxes = [...searchPanel.querySelectorAll('.search-box')]
})

We know this:

  1. The first search box is the origin
  2. The last search box is the destination

We can create a request object from these two search boxes first.

searchPanel.addEventListener('submit', event => {
// ...
const request = {
origin: searchBoxes[0].querySelector('input').value.trim(),
destination: searchBoxes[searchBoxes.length - 1]
.querySelector('input')
.value.trim(),
travelMode: 'DRIVING',
}
})

If there are more than two search boxes, we know there are waypoints. We need to add a waypoints property into the request object.

searchPanel.addEventListener('submit', event => {
// ...
if (searchBoxes.length > 2) {
// Add waypoints property to request object
}
})

Here we know the search boxes in the middle are all waypoints. We can use slice to grab these search boxes.

searchPanel.addEventListener('submit', event => {
// ...
if (searchBoxes.length > 2) {
const waypoints = searchBoxes.slice(1, searchBoxes.length - 1)
}
})

We need to change each waypoint to be an object with two properties: location and stopover. We can use map to construct the object.

searchPanel.addEventListener('submit', event => {
// ...
if (searchBoxes.length > 2) {
const waypoints = searchBoxes
.slice(1, searchBoxes.length - 1)
.map(waypoint => {
return {
location: waypoint.querySelector('input').value.trim(),
stopover: true,
}
})
}
})

Then, we add waypoints to the request object.

searchPanel.addEventListener('submit', event => {
// ...
if (searchBoxes.length > 2) {
// ...
request.waypoints = waypoints
}
})

After creating the waypoints, we’ll draw directions.

searchPanel.addEventListener('submit', event => {
// ...
getDirections(request).then(/*...*/).catch(/*...*/)
})
Directions drawn.

That’s it!