Design Schema/API to have a relation to a public entity from a private one

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
api, backend-api-design

Research direction

No files, tests, or entry points are named. Start by locating the Schema and query definitions, then trace how relation entities are fetched for private and public entities. Done means the API design clearly places fetching on the query definition and preserves the intended private-to-public relation behavior.

Written by the indexing model from the issue text.

Description

Fetching relation entities should not be on the Schema definition, but instead on the query definition

Dominant language
TypeScript
Stars
22
Forks
12
No merged PRs in 30d

Contributor guide

Open the contributing guide

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 graphprotocol/hypergraph

All issues in graphprotocol/hypergraph

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.