Tripletex / Tripletex/tripletex-api2
fullResultSize appears to have changed behavior, breaking pagination for API consumers who rely on it.
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 49
- Forks
- 47
- Avg merge
- 1h 1m
- Merged PRs (30d)
- 1
Description
Since your latest release on 2026-03-16, fullResultSize appears to have changed behavior, breaking pagination for API consumers who rely on it.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100