Request: aggregate fields within relay-style connections
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 3.5k
- Forks
- 468
- Avg merge
- 3h 9m
- Merged PRs (30d)
- 2
Description
I currently have a workload where I need a lot of aggregate information. It would be great to be able to query an aggregate field on Relay-style connection types, similar to the way Supabase handles aggregates. A brief look at PaginationManipulator.php makes it seem like a pretty straightforward thing to implement. I may be willing to implement this feature once a design is fully scoped out.
Contributor guide
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 reading src/Pagination/PaginationManipulator.php and the linked Supabase aggregate documentation to understand how Relay-style connections are assembled. The issue needs a design that defines the aggregate field and its supported behavior before implementation can be considered complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, laravel, php
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100