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

🛠️ Popover: Library

Let’s start by copying everything from main.js into popover.js. As before, we will comment out everything and start anew. We will only uncomment the parts we need.

popover.js
// Copy code here

We will link popover.js to main.js

main.js
import `./popover.js`

Make sure to set main.js as an ES6 modules file.

<script src="/js/main.js" type="module"></script>

We’re ready to begin restructuring the Popover with OOP.

Restructuring with Object Oriented Programming

Object Oriented Programming is about creating instances from a blueprint. We begin our work by creating the blueprint. In this case, we’ll name the blueprint Popover.

I’m going to use Factory functions in this lesson. You are welcome to follow along with any OOP flavour.

export default function Popover() {
// ...
}

We’ll jump straight into the execution part of the code and work backwards. This is the easiest way of figuring out how to refactor. Here’s what we begin with:

// Positions popover
popoverTriggers.forEach(popoverTrigger => {
const popover = getPopover(popoverTrigger) || createPopover(popoverTrigger)
const popoverPosition = calculatePopoverPosition(popoverTrigger, popover)
popover.style.top = `${popoverPosition.top}px`
popover.style.left = `${popoverPosition.left}px`
hidePopover(popover)
})

Since we use forEach to loop through popoverTriggers, we know we need to pass each popoverTrigger into the Popover blueprint.

export default function Popover(popoverTrigger) {
// ...
}

We can use Popover like this:

main.js
import Popover from './popover.js'
const popoverTriggers = document.querySelectorAll('.popover-trigger')
popoverTriggers.forEach(trigger => {
Popover(trigger)
})

Let’s focus on Popover now.

I’ll start changing the name of the popoverTrigger variable. In this case, I chose triggerElement because of two reasons:

  1. The “popover” is redundant since we’re obviously dealing with popovers. trigger alone would suffice.
  2. But trigger can be an action. We aren’t referring to an action in this case. We’re referring to a HTML element, so I added Element as a suffix to make the variable explicit.
export default function Popover(triggerElement) {
// ...
}

For each triggerElement, we searched the DOM for the corresponding popover. If the popover is not found, we create one with JavaScript.

// Old code
popoverTriggers.forEach(popoverTrigger => {
const popover = getPopover(popoverTrigger) || createPopover(popoverTrigger)
// ...
})

We can copy these two lines into the Popover blueprint.

export default function Popover(triggerElement) {
const popover = getPopover(popoverTrigger) || createPopover(popoverTrigger)
}

We need to change popoverTrigger into triggerElement.

export default function Popover(triggerElement) {
const popover = getPopover(triggerElement) || createPopover(triggerElement)
}

I also propose changing popover to popoverElement since we’re referring to the HTML Element.

export default function Popover(triggerElement) {
const popoverElement =
getPopover(triggerElement) || createPopover(triggerElement)
}

Next, we need to decide where to place getPopover and createPopover.

Deciding where to place getPopover and createPopover

There are three solutions:

  1. Place them outside Popover
  2. Placing them both in Popover as methods
  3. Placing them both in Popover as functions

All three choices work. In this case, I’d recommend choosing #3: Placing them both in Popover as functions. We’ll examine all three solutions and I’ll explain why #3 feels like the best approach.

Solution 1: Placing them outside Popover

Here’s the code for getPopover and createPopover.

function getPopover(popoverTrigger) {
return document.querySelector(`#${popoverTrigger.dataset.target}`)
}
function createPopover(popoverTrigger) {
const popover = document.createElement('div')
popover.classList.add('popover')
popover.dataset.position = popoverTrigger.dataset.popoverPosition
// Dynamic id
const id = generateUniqueString(5)
popover.id = id
popoverTrigger.dataset.target = id
const p = document.createElement('p')
p.textContent = popoverTrigger.dataset.content
popover.appendChild(p)
document.body.appendChild(popover)
return popover
}

They already work if you place them outside Popover. Here’s how you’d use them:

export default function Popover(triggerElement) {
const popoverElement =
getPopover(triggerElement) || createPopover(triggerElement)
}

This works, but I find it hard for my brain to wrap around the code.

When I make a blueprint, I like to put all functions and methods related to that blueprint inside the blueprint itself. Functions outside the blueprint serve a different purpose.

Solution 2: Placing them inside Popover as methods

When placing functions inside blueprints, I normally use methods because it’s easier to find them at a glance.

To save getPopover and createPopover as methods, we need to create a common object to store all methods. I’ll use the popover variable in this case.

export default function Popover(triggerElement) {
// ...
const popover = {
getPopover(popoverTrigger) {
// ...
},
createPopover(popoverTrigger) {
// ...
},
}
}

We should rename popoverTrigger to triggerElement since we used triggerElement in Popover.

export default function Popover(triggerElement) {
// ...
const popover = {
getPopover(triggerElement) {
return document.querySelector(`#${triggerElement.dataset.target}`)
},
createPopover(triggerElement) {
const popover = document.createElement('div')
popover.classList.add('popover')
popover.dataset.position = triggerElement.dataset.popoverPosition
// Dynamic id
const id = generateUniqueString(5)
popover.id = id
triggerElement.dataset.target = id
const p = document.createElement('p')
p.textContent = triggerElement.dataset.content
popover.appendChild(p)
document.body.appendChild(popover)
return popover
},
}
}

We can omit the triggerElement parameter since triggerElement is already in the lexical scope.

export default function Popover(triggerElement) {
// ...
const popover = {
getPopover() {
// ...
},
createPopover() {
// ...
},
}
}

We’ll call getPopover and createPopover likes his:

export default function Popover(triggerElement) {
const popoverElement = popover.getPopover() || popover.createPopover()
const popover = {
/*...*/
}
}

It’s not a great experience. We had to write the “popover” word twice in each method call.

export default function Popover(triggerElement) {
// Repeating popover twice makes this code tedious to read
const popoverElement = popover.getPopover() || popover.createPopover()
const popover = {
/*...*/
}
}

We can shorten the name of these two methods by removing the “popover” keyword, but the methods don’t convert the same amount of meaning anymore.

export default function Popover(triggerElement) {
// ... Doesn't convert the same amount of meaning
const popoverElement = popover.get() || popover.create()
const popover = {
/*...*/
}
}

What is popover.get getting? Are we getting the triggerElement? Are we getting popoverElement? Or are we getting something else?

It’s ambiguous.

Likewise popover.create is ambiguous too.

I try not to use ambiguous function/method names because they create unnecessary questions, and in turn, uses unnecessary brainpower.

Solution 3: Placing them in Popover as functions

The cleanest solution I found is to keep the names getPopover and createPopover.

export default function Popover(triggerElement) {
const popoverElement = getPopover() || createPopover()
function getPopover() {
// ...
}
function createPopover() {
// ...
}
const popover = {
/*...*/
}
}

This way: I get to tell my brain getPopover and createPopover are part of Popover. I also get the clarity that I’m getting/creating a popover with these methods.

If I wanted to be super explicit, I can rename getPopover as getPopoverElement. But I think that adds too much friction.

Where to put generateUniqueString?

createPopover uses a getUniqueString function. Again, we can put getUniqueString in three places:

  1. Outside Popover
  2. Inside Popover as a method
  3. Inside Popover as a function

getUniqueString feels more like a helper function. It is generic enough to use in many different components. I tend to keep these functions outside my blueprints, but you can do whatever you want.

Initializing the Popover

Let’s continue inspecting the rest of the code that executes the Popover. Here’s what we’re left with:

popoverTriggers.forEach(popoverTrigger => {
// ...
const popoverPosition = calculatePopoverPosition(popoverTrigger, popover)
popover.style.top = `${popoverPosition.top}px`
popover.style.left = `${popoverPosition.left}px`
hidePopover(popover)
})

We need to calculate the popover’s position with calculatePopoverPosition. We can move this function into Popover as a method.

export default function Popover() {
// Declare variables
// Functions
const popover = {
calculatePopoverPosition(popoverTrigger, popover) {
// ...
},
}
}

We can change popover to popoverElement and popoverTrigger to triggerElement. This conforms with what we have above. (Remember to change the variables inside the function too. I’ll let you do this yourself).

export default function Popover(triggerElement) {
// Declare variables
// Functions
const popover = {
calculatePopoverPosition(triggerElement, popoverElement) {
// ...
},
}
}

We don’t need to pass triggerElement and popoverElement into calculatePopoverPosition they can be found in the lexical scope.

export default function Popover(triggerElement) {
// Declare variables
// Functions
const popover = {
calculatePopoverPosition() {
// ...
},
}
}

To call calculatePopoverPosition, we need to write popover.calculatePopoverPosition.

Let’s eliminate the extra “Popover” keyword. We’ll use change calculatePopoverPosition to calculatePosition.

export default function Popover(triggerElement) {
// Declare variables
// Functions
const popover = {
calculatePosition() {
// ...
},
}
}

We can then use calculatePosition like this:

export default function Popover(triggerElement) {
// Variables
// Functions
const popover = {
/*...*/
}
// Execution
const popoverPosition = popover.calculatePosition()
}

Next, we want to position the popover with the positions we calculated. Here’s the previous code:

popoverTriggers.forEach(popoverTrigger => {
// ...
popover.style.top = `${popoverPosition.top}px`
popover.style.left = `${popoverPosition.left}px`
// ...
})

We can use these two lines directly:

export default function Popover(triggerElement) {
// ...
const popoverPosition = popover.calculatePosition()
popoverElement.style.top = `${popoverPosition.top}px`
popoverElement.style.left = `${popoverPosition.left}px`
}

Finally, we hide the popover with hidePopover.

Hiding the Popover

Here’s the previous code:

popoverTriggers.forEach(popoverTrigger => {
// ...
hidePopover(popover)
})

We can add hidePopover to Popover as a method.

export default function Popover(triggerElement) {
// Variables
// Functions
const popover = {
hidePopover(popover) {
// ...
},
}
// Execution
}

As before:

  1. We’ll change popover to popoverElement.
  2. We don’t need to pass popoverElement since its already in the lexical scope.
  3. We’ll remove the extra “Popover” keyword from the method’s name.

Here’s the optimised version:

export default function Popover(triggerElement) {
// Variables
// Functions
const popover = {
hide() {
// ...
},
}
// Execution
}

We can use hide like this:

export default function Popover(triggerElement) {
// Variables
// Functions
const popover = {
hide() {
// ...
},
}
// Execution
// ...
popover.hide()
}

An aside on hide

popover.hide isn’t very explicit – it suffers from the same problem as popover.get and popover.create.

If we want to be super explicit, we can do something like popoverElement.hide. To do this, we need to add a method to popoverElement.

export default function Popover() {
popoverElement.hide = function () {
// ...
}
}

Be careful of doing this because you’ll create a non-standard HTML element. When you work in teams, you may mislead people into thinking HTML Elements have the hide method. (Which is not good).

If you insist on standardisation and consistency, you can create a function called hidePopover inside Popover instead.

export default function Popover() {
// ...
function hidePopover() {
// ...
}
// ...
}

I don’t like this because the extra function tells me there’s another exception I need to watch out for – which uses brain energy – and it’s something I’m reluctant to do.

So popover.hide is a happy-enough medium for me right now, and I don’t bother to refactor more.

(Protip: Good enough solutions are good enough. Move on when you think it’s good enough! If you come back to it and it irritates you, you still have the chance to refactor).