You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: packages/utils/plugins-helpers/src/types.ts
+92-2
Original file line number
Diff line number
Diff line change
@@ -89,15 +89,105 @@ export namespace Types {
89
89
[url: string]: UrlSchemaOptions;
90
90
}
91
91
92
-
exporttypeLocalSchemaPath=string;
92
+
/**
93
+
* @additionalProperties false
94
+
* @description Loads a schema a local file or files, with customized options for parsing/loading.
95
+
*/
96
+
exportinterfaceLocalSchemaPathOptions{
97
+
/**
98
+
* @description Skips checks for graphql-import syntax and loads the file as-is, without imports support.
99
+
* @default true
100
+
*/
101
+
skipGraphQLImport?: boolean;
102
+
103
+
/**
104
+
* @description Converts all GraphQL comments (`#` sign) to descriptions during the parse phase, to make it available
105
+
* for plugins later.
106
+
* @default false
107
+
*/
108
+
commentDescriptions?: boolean;
109
+
110
+
/**
111
+
* When building a schema from a GraphQL service's introspection result, it
112
+
* might be safe to assume the schema is valid. Set to true to assume the
113
+
* produced schema is valid.
114
+
*
115
+
* @default false
116
+
*/
117
+
assumeValid?: boolean;
118
+
119
+
/**
120
+
* Set to true to assume the SDL is valid.
121
+
*
122
+
* @default false
123
+
*/
124
+
assumeValidSDL?: boolean;
125
+
126
+
/**
127
+
* By default, the parser creates AST nodes that know the location
128
+
* in the source that they correspond to. This configuration flag
129
+
* disables that behavior for performance or testing.
130
+
*
131
+
* @default false
132
+
*/
133
+
noLocation?: boolean;
134
+
135
+
/**
136
+
* If enabled, the parser will parse empty fields sets in the Schema
137
+
* Definition Language. Otherwise, the parser will follow the current
138
+
* specification.
139
+
*
140
+
* This option is provided to ease adoption of the final SDL specification
141
+
* and will be removed in v16.
142
+
*
143
+
* @default false
144
+
*/
145
+
allowLegacySDLEmptyFields?: boolean;
146
+
147
+
/**
148
+
* If enabled, the parser will parse implemented interfaces with no `&`
149
+
* character between each interface. Otherwise, the parser will follow the
150
+
* current specification.
151
+
*
152
+
* This option is provided to ease adoption of the final SDL specification
153
+
* and will be removed in v16.
154
+
*
155
+
* @default false
156
+
*/
157
+
allowLegacySDLImplementsInterfaces?: boolean;
158
+
159
+
/**
160
+
* EXPERIMENTAL:
161
+
*
162
+
* If enabled, the parser will understand and parse variable definitions
163
+
* contained in a fragment definition. They'll be represented in the
164
+
* `variableDefinitions` field of the FragmentDefinitionNode.
165
+
*
166
+
* The syntax is identical to normal, query-defined variables. For example:
167
+
*
168
+
* fragment A($var: Boolean = false) on T {
169
+
* ...
170
+
* }
171
+
*
172
+
* Note: this feature is experimental and may change or be removed in the
173
+
* future.
174
+
*
175
+
* @default false
176
+
*/
177
+
experimentalFragmentVariables?: boolean;
178
+
}
179
+
exportinterfaceLocalSchemaPathWithOptions{
180
+
[globPath: string]: LocalSchemaPathOptions;
181
+
}
182
+
93
183
exporttypeSchemaGlobPath=string;
94
184
/**
95
185
* @description A URL to your GraphQL endpoint, a local path to `.graphql` file, a glob pattern to your GraphQL schema files, or a JavaScript file that exports the schema to generate code from. This can also be an array which specifies multiple schemas to generate code from. You can read more about the supported formats [here](schema-field#available-formats).
0 commit comments