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

`/project` endpoint does not include closed project

Open
#101 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Domain
api

Research direction

Start by tracing the /project?id=myId, /project?id=myId&isClosed=true, and /project/myId entry points and compare how each handles closed projects. Check the existing API behavior or tests for project lookup, then verify that the list and single-project requests agree on the expected closed-project result.

Written by the indexing model from the issue text.

Description

We have a project which is closed (isClosed = true). Let's say it's ID is myId

  • When I call /project?id=myId I get an empty response.
  • When I call /project?id=myId&isClosed=true the response is still empty.

Whereas

  • When I call /project/myId the project is correctly returned.

Is this expected behavior?

Dominant language
No language data
Stars
49
Forks
47
Avg merge
1h 1m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 Tripletex/tripletex-api2

All issues in Tripletex/tripletex-api2

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.