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

Say when a collection item is skipped for a bad slug

Open
  • Is something wrong?
#166 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript, react
Domain
full-stack

Research direction

Start with packages/builder-server/src/services/collectionService.js to see how invalid slugs are skipped, then read packages/editor-ui/src/pages/CollectionItems.jsx and its existing invalid-item notice. Add visibility for skipped items or repair their slugs, and add a test; done means users can see the affected item or it is repaired.

Written by the indexing model from the issue text.

Description

bug

A collection item with a broken address disappears with nothing on screen to say so.

Since 0fd5005a, readCollectionItems (collectionService.js) skips an item whose stored slug (raw.slug ?? raw.id) is missing or not ^[a-z0-9-]+$, with a server-side console.warn only. The editor list, link pickers and export then simply lack the item, with nothing on screen to explain it. Such files come only from a hand-edited project or a crafted backup (writes always produce plain slugs), so this is about not losing content silently, not about frequency. Likely shapes: report skipped items on the collection screen (as the invalid-item notice does), or repair the slug from the file name.

Done when: A skipped item is visible to the user (or repaired), with a test.

Start: collectionService.js, CollectionItems.jsx. Source: 2026-10-06 review of the containment fix.

Dominant language
JavaScript
Stars
162
Forks
6
Avg merge
12h 55m
Merged PRs (30d)
2

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

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 tsiger/widgetizer

All issues in tsiger/widgetizer

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.