Skip to content

Clarify input coercion rule algorithms. #234

Closed
@leebyron

Description

@leebyron

During graphql/graphql-js#553 I realized that previously some cases were ignoring bad input replacing it with null or undefined rather than rejecting it. Most of these cases were at items in lists or fields in input objects.

This sort of mistake would be harder to make if the spec made the algorithms for input coercion more clear with steps rather than prose.

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