graph-client
graph-client copied to clipboard
The Graph library for building GraphQL-based dapps in a decentralized way.
It seems that we're locked into depedencies which will only work on Node v16. Unfortuantely even AWS isn't supporting v16 yet which means we're blocked from using this. I have...
This architecture is really awesome. if we could have a health-check endpoint to get `chainHeadBlock`, its also helpful. I think the following is an ideal configuration. Current configuration ==> >...
`graph-node` has limitations on query complexity/weight (https://github.com/graphprotocol/graph-node/blob/5732ddfdd4496773a68593aa6705bbc96e70bdf2/graphql/src/execution/query.rs#L574). We can detect those ahead of time and warn the user, instead of failing at runtime.
Today, `graph-node` Subscriptions transport is not 100% reliable and uses a legacy protocol. We are looking into different ways of providing an alternative to that. Possible solutions: - subscribe-as-query: write...
This is an open issue to discuss the option to add some metadata in `graph-node` responses, using the `extensions` field of GraphQL response.
Running into this error while trying to load Graph Client with Apollo and Next.js. Relevant code might be here: https://github.com/schmidsi/hackathon-starterkit/blob/main/frontend/lib/apolloClient.js
[![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [eslint](https://eslint.org) ([source](https://togithub.com/eslint/eslint)) | [`8.25.0` -> `8.26.0`](https://renovatebot.com/diffs/npm/eslint/8.25.0/8.26.0) |...
Hello there! I found the bug in latest versions of `@graphprotocol/client-cli` and `@graphprotocol/client-add-source-name`. When I try to implement cross-chain query like in your example I can't build my project because...
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically....