Skip to content

Engineering / Open resources

Congresso

Event and registration management, with an attendee frontend and an orchestration API.

Open repository

Contribution tasks

Proposals based on source inspection, awaiting maintainer review. Check the current version and existing issues before submitting. The link opens a draft: you review it and decide whether to publish.

Source inspected on

Return 404 when looking up an unknown lecture

LectureController.find calls findOne and then reads lecture.length. With no match, lecture is null and that access reaches the 500 error handler. The frontend builds lecture links from slugs; an unknown slug needs a predictable not-found response.

Estimated size
S · 1–3 hours
Skills
JavaScript · Express · Mongoose

Files and evidence

Step-by-step acceptance criteria

  1. Add a regression for GET /lecturies/find/unknown-slug with findOne returning null.
  2. Replace the length access with a missing-document check and return 404 using the existing sendResponse format.
  3. Verify a valid document still returns 200 with its data and a database rejection still returns 500.
  4. Document the three cases and the test command in the PR; use local fixtures without relying on the production database.
Review draft on GitHub

How to start contributing

Links come from the portfolio catalog; check availability, license and open tasks in each repository. Read the README and license, run the project and propose a small documentation improvement or a reproducible test case. Discuss larger changes with the maintainer first.

Read the README

Project evidence