• Use a meaningful title for the pull request. Include the name of the package modified.
• Test the change in your own code. (Compile and run.)
• Add or edit tests to reflect the change. (Run with npm test.)
• Follow the advice from the readme.
• Avoid common mistakes.
• Run npm run lint package-name (or tsc if no tslint.json is present).
• Provide a URL to documentation or source code which provides context for the suggested changes: https://graphql.org/graphql-js/type/#graphqlobjecttype
• [n/a] Increase the version number in the header if appropriate.
• [n/a] If you are making substantial changes, consider adding a tslint.json containing { "extends": "dtslint/dt.json" }.

This builds off of some changes from #22789 and continues having TArgs be optional. This is not a breaking change. It's possible that unknown is a better option for TArgs; however, that would be TS3 specific and be a breaking change.

This change is to allow overriding TArgs in more places. For example, allowing any args or to restrict args further. This primarily impacts the GraphQLFieldConfigMap and GraphQLObjectType types.

Using GraphQLFieldConfigMap with generics:

const Query = new GraphQLObjectType({
  fields: (): GraphQLFieldConfigMap<void, Context, any> => ({
    someField: getFieldConfig(),
  })
});

Using GraphQLObjectType with generics:

const Query = new GraphQLObjectType<void, Context, any>({
  fields: () => ({
    someField: getFieldConfig(),
  })
});