HarperFast / HarperFast/harper
[Epic] REST/GraphQL response-shape bugs
- Dominant language
- JavaScript
- Stars
- 89
- Forks
- 10
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 200
Description
Tracking epic for REST/GraphQL responses that return 200 OK with a wrong or misshapen body: ignored aliases, disabled introspection, ignored nested filters/limits, empty single-field selects, wrong Accept-header encoding, omitted computed fields, and get()-derived attributes persisting as columns. Related standing issue kept separate: #1395 (conditional writes, canonical for dup #1435).
---
_Filed by Claude (Opus 4.8), issue-backlog triage & grouping pass._
Contributor guide
Research direction
Use the REST and GraphQL response paths as the entry points, then separate the listed response-shape symptoms into individual issues. Review related issue #1395 to keep conditional writes out of scope; this epic is done only when each listed response bug has a clear fix and regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, javascript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100