Types for input objects should not have a prototype

[bezreyhan]

Describe the bug

The Javascript object that is returned for mutation inputs does not have a prototype but this is not reflected in the generated types.

See issue here: ardatan/graphql-tools#1374

To Reproduce
Steps to reproduce the behavior:

2. My GraphQL operations:

{
  Mutation: {
    someMutation(_, { input }) {
        input.hasOwnProperty() // this will throw an error since input does not have a prototype
    } 
  }
}

3. My codegen.yml config file:

overwrite: true
schema: '...'
documents: null
generates:
  src/...
    config:
      noSchemaStitching: true
      useIndexSignature: true
      namingConvention:
        enumValues: 'change-case#upperCase'
    plugins:
      - add:
          content: '/* tslint:disable */'
      - 'typescript'
      - 'typescript-resolvers'

Expected behavior

Can we create a special type for object-inputs to null out all of their prototype fields?

[Urigo]

Hi @bezreyhan and thank you for the report!

Sorry but I'm not adding a lot here but just labeling it according to our new Contribution Guide and issue flow.

It seems like we are on stage 0.
Now in order to advance to stage 1 we'll need an easily running reproduction, do you think you can create that on code sandbox?
After that, maybe someone can help with advancing it into stage 2 by creating a failing test?

Thank you and sorry that this comment is not a complete solution (yet).

[dotansimha]

@bezreyhan I think I need more context here. Why does the codegen types effect this? we just use { ... } to define the TS types. Is there an alternative way for this?