graphprotocol / graphprotocol/hypergraph

Schema API improvements

Open
#8 0 comments 0 reactions 1 assignee View on GitHub

@nikgraf is already working on this.

Since Nov 6, 2024.

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

Description

createEntity

  • allow to created nested entities
  • allow to created nested entities (recursively)
  • typing for creating nested entities
  • typing for creating nested entities (recursively)
  • schema validation for nested entities?
  • relations should be defined on both end
  • decide and implement how relations are stored
  • allow to provide IDs for relations ["abc", "def"]
  • allow to mix objects and IDs for relations ["abc", { id: "def", name: "lala" }] (if id: def exists it's an upsert for the attributes that are included)
  • make all fields optional
  • add implicit entity properties (e.g. name, description, cover)
  • make sure to only return get fields which are defined in the query

useQuery

  • resolve nested entities
  • resolve nested entities (recursively)
  • typing for nested entities
  • typing for nested entities (recursively)
  • filters for text, number, checkbox
  • reverse relationship queries?
  • make all fields optional
  • always include the id and types
  • return array instead of object
  • handle circular dependencies
  • add implicit entity properties (e.g. name, description, cover)

getById

  • implement

updateEntity

  • implement

deleteEntity

  • implement

setTriple

  • define API

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.