Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

fix(delete-user-data): kit/extension parity – spaces in EXT_SELECTED_EVENTS silently drop events

Open Beginner friendly
#3,259 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@CorieW is already working on this.

Since Oct 20, 2026.

  • #3286 by @CorieW — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
firebase, typescript
Domain
backend

Research direction

Start in kits/delete-user-data/src/events.ts at setupEventChannel and trace how EXT_SELECTED_EVENTS is passed to channel(). Check how the kit handles comma-separated values with surrounding spaces and empty entries; done means all non-empty trimmed event types are accepted, with an empty result treated as unset.

Written by the indexing model from the issue text.

Description

kits type: bug

delete-user-data kit/extension parity. Priority: low. A hand-written event list with spaces silently stops some events.

Difference
  • Extension: the platform writes EXT_SELECTED_EVENTS from the types picked at install, with no spaces, so every selected type is published. (ext:export also writes it without spaces.)
  • Kit: users write EXT_SELECTED_EVENTS by hand in .env. firebase-admin splits it on , without trimming, so a, b, c allows a but not " b" or " c". Every type after the first is dropped, with no warning.
Reproduced

EXT_SELECTED_EVENTS=firebase.extensions.delete-user-data.v1.firestore, firebase.extensions.delete-user-data.v1.database, firebase.extensions.delete-user-data.v1.storage

  • Extension (all three selected): published firestore, database and storage.
  • Kit: published only firestore.
Code
Resolution

In setupEventChannel, pass an array: selectedEvents.split(",").map((s) => s.trim()).filter(Boolean). Treat an empty result the same as unset.

Dominant language
TypeScript
Stars
978
Forks
433
Avg merge
20h 44m
Merged PRs (30d)
17

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from firebase/extensions

All issues in firebase/extensions

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.