Why template arguments?

graphql · Jun 20, 2020 · aa6ddc6 · aa6ddc6
1 parent c609839
commit aa6ddc6
Showing 1 changed file with 6 additions and 0 deletions.
diff --git a/src/type/definition.d.ts b/src/type/definition.d.ts
@@ -366,6 +366,9 @@ export interface GraphQLScalarTypeConfig<TInternal, TExternal> {
  * your library or project. Do not use a shortened identifier as this increases
  * the risk of conflicts. We recommend you add at most one extension field,
  * an object which can contain all the values you need.
+ *
+ * We've provided these template arguments because this is an open type and
+ * you may find them useful.
  */
 export interface GraphQLObjectTypeExtensions<TSource = any, TContext = any> {
   [attributeName: string]: any;
@@ -493,6 +496,9 @@ export interface GraphQLResolveInfo {
  * your library or project. Do not use a shortened identifier as this increases
  * the risk of conflicts. We recommend you add at most one extension field,
  * an object which can contain all the values you need.
+ *
+ * We've provided these template arguments because this is an open type and
+ * you may find them useful.
  */
 export interface GraphQLFieldExtensions<
   TSource,