Skip to content

Field produces both value and error #769

@tomgatzgates

Description

@tomgatzgates

I'm looking to clarify whether it should be valid for a field to be resolved with both a value and an error in the global errors list.

This scenario came up when resolving a field to an external service. In the event that the external service is down, the server would like to provide a sensible default response whilst still notifying the client that the value is a fallback value.

Its technical possible to achive but I'm wondering whether it is/should be valid as per the spec?

cc @eapache

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions