Mokhtar Naamani 8c6424f12f hydra-cli 0.0.20 hace 4 años
..
bootstrap 835b9dc8fd remove hydra related code hace 4 años
mappings 8a0ef268b8 fix: update referenced entities on EntityPropertyValuesUpdated hace 4 años
scripts 99aca3000b add script to get content-dir classes(id,name) from the chain hace 4 años
.env fa2ceae725 query-node: fix network-name hace 4 años
.gitignore 76916dfdd6 query-node: do not check in generated code hace 4 años
README.md ea241cf9f7 query-node: fix build scripts and remove generated code from yarn workspace hace 4 años
build.sh f662b6fdda query-node: clean build hace 4 años
indexer-tsconfig.json bdb01a7d87 add esModuleInterop flag to indexer-tsconfig.json hace 4 años
package.json 8c6424f12f hydra-cli 0.0.20 hace 4 años
run-tests.sh 547b64d070 start scripts forgot to bring up graphql-server hace 4 años
schema.graphql 75992f7315 keep track of the next entity id hace 4 años
tsconfig.json 94e8fb7ae8 Query node - fix @joystream/types issue hace 4 años
typedefs.json ca0f390137 update typedefs from types hace 4 años

README.md

query-node

The query-node project contains an input schema (schema.graphql) and mappings for the Joystream content-directory runtime module.

Code generation

We use Hydra-cli to generate a graphql server and a block indexer for joystream chain:

$ cd query-node
$ yarn build

Run mapping processor

Before running mappings make sure indexer(yarn indexer:start) and indexer-api-server (mappings get the chain data from this graphql server) are both running:

yarn processor:start

Query data

Once processor start to store event data you will be able to query this data from http://localhost:4002/graphql.

query {
  channels {
    title
  }
}