Skip to content

[Feature] Declarative Call Enforcement #6211

@Data-Nexus

Description

@Data-Nexus

Description

We have run into some declarative calls failing. In our mappings we utilize the try_{ethCall} in order to get things like token.name, token.symbol, token.decimals however in rare circumstances contracts will not have this functionality. Rather than failing the subgraph I would prefer that declarative calls simple try to make the eth call.

Are you aware of any blockers that must be resolved before implementing this feature? If so, which? Link to any relevant GitHub issues.

No response

Some information to help us out

  • Tick this box if you plan on implementing this feature yourself.
  • I have searched the issue tracker to make sure this issue is not a duplicate.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions