Add support of INPUT_FIELD_DEFINITION location

[FluorescentHallucinogen]

Currently, @constraint supports only ARGUMENT_DEFINITION directive location.

Problem: e.g. Prisma extracts all query/mutation arguments to separate input types when generates schema from datamodel.

Please add support of INPUT_FIELD_DEFINITION location to be able to apply @constraint to input type fields. E.g.:

type User {
  name: String
  phone: String
  email: String
  ...
}

...

type Mutation {
  createUser(data: UserCreateInput!): User!
  updateUser(data: UserUpdateInput!, where: UserWhereUniqueInput!): User!
  deleteUser(where: UserWhereUniqueInput!): User
  ...
}

...

input UserUpdateInput {
  name: String
  phone: String
  email: String @constraint(format:"email")
  ...
}

[ecker00]

Is this working as it was merged? I've tested a bit on v3.2.2, but still don't see any effect when using it on an input.

[FluorescentHallucinogen]

@ecker00

Is this working as it was merged?

It seems you have confused. PR #4 was merged, but it fixes a completely different issue. Currently there is no PR that adds support of INPUT_FIELD_DEFINITION location.

BTW, pull requests are welcome. 😉

[FluorescentHallucinogen]

Looks like objects validation rules proposed in #13 can solve the problem of input type fields validation. Moreover, objects validation approach opens up more possibilities like compounded validation: checking the value of multiple fields at the same time. It seems this can't be covered using the INPUT_FIELD_DEFINITION approach. @vsimko Please correct me if I'm wrong.

[hashinclude72]

please fix this, still no update ..... or if there will no updates could you tell me ay other package for Lambda

[vsimko]

Unfortunately, I don't have enough time to work on this package at the moment.
Is there anybody that would like to contribute ?