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

fullResultSize appears to have changed behavior, breaking pagination for API consumers who rely on it.

Open
#127 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Domain
api

Research direction

Start by reproducing the reported fullResultSize behavior in the latest release and comparing it with the prior behavior described in the issue. Trace the API pagination response for consumers and identify the expected result size semantics; done when the behavior is isolated and covered by a regression check.

Written by the indexing model from the issue text.

Description

Since your latest release on 2026-03-16, fullResultSize appears to have changed behavior, breaking pagination for API consumers who rely on it.

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

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.