Skip to content

improving response for index-node subgraph features API #5127

Open
@saihaj

Description

@saihaj

I think it is built in assumption that if you give an ID of subgraph you will get result back. But in the case where we cannot find that ID it just throws.

So we can either consider making index-node API that field be non-null or we have union of responses where we can define the error message of NotFound https://blog.logrocket.com/handling-graphql-errors-like-a-champ-with-unions-and-interfaces/

image

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions