Executive Summary
There are many great things that team has worked on. Our focus has been constantly to improve developer experience and making it easier for users to try out new features and help out with migration to Studio and Network. Our team was on a company offsite this month and discussed various things we want to bring to graph-tooling
, graph-node
and help making it easier for builders to build on the graph. As we look ahead there are lot of features we want to help build and help the the ecosystem grow. We are working on writing out proposals and will share more details in coming weeks!
Looking back (what was delivered)
-
graph-tooling
- Base mainnet support Adding base mainnet to staging by pranavdaa · Pull Request #1398 · graphprotocol/graph-tooling · GitHub
- Improvements to Substream powered subgraph DX
- fix: do not exit with 1 for substreams by saihaj · Pull Request #1384 · graphprotocol/graph-tooling · GitHub
- fix: only ask for subgraph name and directory for init examples by saihaj · Pull Request #1382 · graphprotocol/graph-tooling · GitHub
- fix: init from example improvements by saihaj · Pull Request #1393 · graphprotocol/graph-tooling · GitHub
- Ask for start block in graph add fix: ask for start block in graph add if we fail to fetch it from chain by saihaj · Pull Request #1400 · graphprotocol/graph-tooling · GitHub
- Do not hang on deploy key failures fix: do not hang on deploy key failure by saihaj · Pull Request #1402 · graphprotocol/graph-tooling · GitHub
- Do not ask for local path when adding more contracts in init fix: do not ask for local path when adding more contracts in init by saihaj · Pull Request #1403 · graphprotocol/graph-tooling · GitHub
- Fix derived loader failing for entities with Bytes as IDs cli: Fix derived loader failing for entities with Bytes as ids by incrypto32 · Pull Request #1406 · graphprotocol/graph-tooling · GitHub
- Introduce a
--skip-install
flag forgraph init
feat: skip install flag for init by saihaj · Pull Request #1407 · graphprotocol/graph-tooling · GitHub - Fix ABI endpoint for ZKSync mainnet cli: fix ABI api endpoint zksync mainnet by uF4No · Pull Request #1410 · graphprotocol/graph-tooling · GitHub
- Add support for Arweave file datasources feat: arweave file datasource by saihaj · Pull Request #1411 · graphprotocol/graph-tooling · GitHub
- When we first started onboarded as maintainer for this project on CLI we identified a lot of tech debt and lack of test coverage. Our strategy was to first get familiar with the project and get it to a shape where we can start fixing some bugs and introduce new features, to keep the momentum going for our users. But as we want to do more complex features or fix bugs there we simply cannot keep adding to tech debt. So we did some explorations. Notable we want to improve the DX for the
subgraph.yaml
file feat: use zod to parse the yaml by saihaj · Pull Request #1394 · graphprotocol/graph-tooling · GitHub this was trying to clean up a lot of code, make it more type safe and for end users we could provide auto-complete functionality. But this was becoming a big refactor touching many critical pieces and lack of test coverage in the CLI makes it harder to safely roll out to users. So we started to explore a new core package who’s idea is to provide functionality of CLI by composing functions. We want to add test coverage to all these methods and once we have some critical flows working we will swap usage of CLI with these utility functions. This is a very large refactor effort which we will keep on-going on the side and this is something important since this will also help us provide better errors, address bugs that today we can’t resolve easily and unlocks many other things!
-
subgraph-cacher
Previously we were working on a caching proxy that makes it more attractive for dapps to move to the network. GitHub - the-guild-org/maverick-subgraph but as we got introduced to more dApps and realized the performance limitation in the
graph-client
setup we decided to create a hosted solution that makes it easier for anyone to cache any subgraph. Checkout our post to learn more about features we support today Subgraph Cacher. If this is something you would want to use in please get in touch! -
graph-node
- Landed GraphQL over HTTP compliance https://github.com/graphprotocol/graph-node/pull/4507
- Nested sorted by interface ready is merged, will got out in next release Nested Sorting: interface by non-derived child entity by kamilkisiela · Pull Request #4058 · graphprotocol/graph-node · GitHub
- Address feedback on
graphman
API - Working on proposal for GraphQL V2 API. Will share more details in coming weeks!
-
indexer
Investigate memory leaks. First thing we noticed is it supports many old Node.js version and we want to focus on current stable LTS version and minimize surface area from various runtime versions.
-
docs
- Help with code reviews and fix deploy issues
Looking ahead (upcoming priorities)
-
graph-tooling
- Figure out ways to make it easier to migrate to Studio
-
graph-node
- Working on
Timestamp
scalars - GraphQL Over HTTP Support rollout
- Address feedback on
graphman
API and devise a rollout strategy - Share a proposal for GraphQL V2 endpoint
- Working on
-
indexer
We are going to start help maintain pieces for the indexer stack. Working with Edge and Node team to figure out good first issues and build out a roadmap of items we want to do on this.
-
docs
- Integrate docs
- Open Graph image service for docs that will improve sharing experience opengraph image service · Issue #402 · graphprotocol/docs · GitHub
- Improving redirects for subitems in remote docs improving redirects for subitems in docs · Issue #436 · graphprotocol/docs · GitHub
- Add documentation for
Int8
Add docs for `Int8` scalar · Issue #396 · graphprotocol/docs · GitHub
-
substreams-js
Help building out the PoC from the wireframes for registry
-
subgraph-cacher
If there are users trying to use this service, we are happy to provide resources and work with them to support use cases and make their transition to network easier!