2022-07-07
1719
#react
Iniubong Obonguko
123397
Jul 7, 2022 ⋅ 6 min read

Using custom events in React

Iniubong Obonguko Frontend developer, Vue ninja, code enthusiast. Learning every day.

Recent posts:

Fix over-caching with dynamic IO caching in Next.js 15

Next.js 15 caching overhaul: Fix overcaching with Dynamic IO and the use cache directive.

David Omotayo
Aug 6, 2025 ⋅ 10 min read
LLMs are facing a QA crisis here’s how we could solve it

LLMs are facing a QA crisis: Here’s how we could solve it

LLM QA isn’t just a tooling gap — it’s a fundamental shift in how we think about software reliability.

Rosario De Chiara
Aug 4, 2025 ⋅ 7 min read

Windsurf vs. Cursor: When to choose the challenger

Windsurf AI brings agentic coding and terminal control right into your IDE. We compare it to Cursor, explore its features, and build a real frontend project.

Chizaram Ken
Jul 31, 2025 ⋅ 9 min read

The CSS if() function: Conditional styling will never be the same

The CSS Working Group has approved the if() function for development, a feature that promises to bring true conditional styling directly to our stylesheets.

Ikeh Akinyemi
Jul 30, 2025 ⋅ 12 min read
View all posts

2 Replies to "Using custom events in React"

  1. Custom events are also known as “synthetic” events.

    You need to check this statement. Synthetic events are react wrappers over native HTML events. Custom events are what you described in your article.

  2. For unsubscribe to work you need to pass the initial function. So unsubscribe(“hideList”); need the pointer to the function.

    So:
    let f = setIsOpen(false);
    subscribe(“hideList”, f);

    and later:
    return () => {
    unsubscribe(“hideList”,f);
    }

Leave a Reply