Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

resolver - _meta.block.number

Open
  • Is something wrong?
#739 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
graphql, typescript
Domain
api, backend-api-design

Research direction

Start by tracing how @resolveTo handles sourceFieldName and requiredSelectionSet, then inspect how the block-tracking-plugin exposes _meta.block.number. Done means the provided Lock extension can resolve blockNumber: Int! from the unlock source without breaking existing resolver behavior.

Written by the indexing model from the issue text.

Description

Hi,

is it possible to extend a graphql type with a block number of the block-tracking-plugin?
e.g. ...

extend type Lock {
      blockNumber: Int! @resolveTo(
        sourceName: "unlock"
        sourceTypeName: "Query",
        sourceFieldName: "_meta",
        requiredSelectionSet: "{ block { number } }",
        sourceArgs: {}
     )
}

Thanks :)

Dominant language
TypeScript
Stars
186
Forks
49
No merged PRs in 30d

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

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.

More from graphprotocol/graph-client

All issues in graphprotocol/graph-client

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.