graphprotocol / graphprotocol/hypergraph
proposal: Computed data queries
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 22
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
Sometimes we want to query data using a dynamic query that isn't supported in hypergraph, and instead of returning an entity, we might want to return a computed value.
For example, there are a set of entities with the Episode type. Each episode points to a Podcast. I might want to calculate how many episodes a podcast has.
This would require a mechanism for users to specify queries to make against the graph with syntax for aggregations, selecting, filtering, etc. We could make it type safe by integrating it with our schema language.
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
No implementation files, tests, or entry points are named. Start by surveying the existing hypergraph query and schema-language APIs, then define the scope and acceptance criteria for aggregations, selection, filtering, and computed values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100