Skip to content

wrong input for coercion should produce a field error #459

Closed

Description

@andimarek

Because of the recent changes to Scalars/Enum serialize throws now an exception for a wrong input.

This is currently not handled correctly: it aborts the complete execution, but it should cause an error and the value should be set to null.

See 66c9a5c#diff-2ca75b50e4e550b9f58dd03d3c28782cR69 for a test

Activity

  1. added this to the milestone on May 24, 2017
  2. self-assigned this
    on May 24, 2017
  3. andimarek commented on Jun 5, 2017

    @andimarek
    MemberAuthor

    Fixed in #487

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions