Parsing silently fails for mutations

Consider this example:

# Schema
type LogInput {
  message: String!
  createdAt: Date!
}

type Log {
  id: ID!
  message: String!
  createdAt: Date!
}

type Mutation {
  createLog(log: LogInput!): Log!
}

# query
mutation {
  createLog({
    message: "Hello, World!",
    createdAt: "2017-01-001" # invalid
  }) {
    message,
    createdAt
  }
}

In this example, parsing silently fails and sets the createdAt to null. I think it would be more useful to thrown an error in this case.

[excitement-engineer]

I have release version 3.4.0 which includes the fix.

[jhnferraris]

Can anyone confirm if the parsing silently fails on GraphQLDateTime on version ^3.5.0 with graphql version 0.13.2?

I have this schema snippet

input payload{
    durationStart: GraphQLDateTime!
    durationEnd: GraphQLDateTime!
  }

mutation {
  sendSchedule(payload: {
    durationStart:"04-04 14:59:59xxxxx" # invalid
    durationEnd: "2018-04-04T15:00:00"
  }) {
     durationStart
     durationEnd
  }
}

In the resolver args.payload log is showing:

durationStart: '04-04 14:59:59xxxxx',
durationEnd: '2018-04-04T15:00:00

therefore it is “passing”?

Thanks for the assist!

UPDATE:

My bad. I just set it up the wrong way. 😄 I referred here for the solution: https://github.com/excitement-engineer/graphql-iso-date/issues/37#issuecomment-304286628