Mokhtar Naamani 0e590e9387 query-node: configure WS_PROVIDER_ENDPOINT_URI in docker-compose file hace 4 años
..
bootstrap 835b9dc8fd remove hydra related code hace 4 años
generated 8ece43bb6f query-node: use custom index-builder-lib hace 4 años
index-builder 60e19640fa index-builder: strange build error '@ts-ignore'ing for now hace 4 años
mappings 9b91908678 query-node: fix "happenedIn" property not defined VideoMediaEncoding graphql schema hace 4 años
.dockerignore 6c76f7d0d6 query-node: ensure building of index-builder hace 4 años
.env e81df555c6 WIP - refactoring query_node hace 4 años
.gitignore 6c76f7d0d6 query-node: ensure building of index-builder hace 4 años
README.md 2eec0339f0 update readme.md hace 4 años
docker-compose.yml 0e590e9387 query-node: configure WS_PROVIDER_ENDPOINT_URI in docker-compose file hace 4 años
package.json 5f27cd5e62 query-node: do not do postinstall in query-node its running before @joystream/types get built hace 4 años
run-tests.sh 0e590e9387 query-node: configure WS_PROVIDER_ENDPOINT_URI in docker-compose file hace 4 años
schema.graphql 86a14a5067 add happenedIn field to Language and VideoMediaEncoding entities hace 4 años
tsconfig.json dff8a36993 query-node: update tsconfig 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
$ hydra-cli codegen

After codegen process is done, we must add this lines to the indexer/tsconfig.json file. It is required because we are using joystream/types for decoding chain data in the mappings:

{
  "compilerOptions":
    ...
    "baseUrl": ".",
    "paths": {
      "@polkadot/types/augment": ["../../node_modules/@joystream/types/augment-codec/augment-types.ts"]
    }
}

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
  }
}