Support for oneOf and union types

Related to #197

Signed-off-by: Alan Cha <[email protected]>

Author: Alan-Cha

packages/openapi-to-graphql/lib/index.d.ts

@@ -3,14 +3,14 @@
  *
  * Some general notes:
  *
- * - GraphQL interfaces rely on sanitized strings for (Input) Object Type names
+ * - GraphQL interfaces rely on sanitized strings for (input) object type names
  *   and fields. We perform sanitization only when assigning (field-) names, but
  *   keep keys in the OAS otherwise as-is, to ensure that inner-OAS references
  *   work as expected.
  *
- * - GraphQL (Input) Object Types must have a unique name. Thus, sometimes Input
- *   Object Types and Object Types need separate names, despite them having the
- *   same structure. We thus append 'Input' to every Input Object Type's name
+ * - GraphQL (input) object types must have a unique name. Thus, sometimes Input
+ *   object types and object types need separate names, despite them having the
+ *   same structure. We thus append 'Input' to every input object type's name
  *   as a convention.
  *
  * - To pass data between resolve functions, OpenAPI-to-GraphQL uses a _openapiToGraphql object

packages/openapi-to-graphql/lib/index.js

@@ -7,9 +7,9 @@ import { Oas3, ServerObject, ParameterObject, SchemaObject, OperationObject, Res
 import { PreprocessingData, ProcessedSecurityScheme } from './types/preprocessing_data';
 import { InternalOptions } from './types/options';
 export declare type SchemaNames = {
-    fromPath?: string;
-    fromSchema?: string;
     fromRef?: string;
+    fromSchema?: string;
+    fromPath?: string;
     /**
      * Used when the preferred name is known, i.e. a new data def does not need to
      * be created

packages/openapi-to-graphql/lib/oas_3_tools.d.ts

@@ -11,10 +11,10 @@ export declare function preprocessOas(oass: Oas3[], options: InternalOptions): P
 /**
  * Method to either create a new or reuse an existing, centrally stored data
  * definition. Data definitions are objects that hold a schema (= JSON schema),
- * an otName (= String to use as the name for Object Types), and an iotName
- * (= String to use as the name for Input Object Types). Eventually, data
- * definitions also hold an ot (= the Object Type for the schema) and an iot
- * (= the Input Object Type for the schema).
+ * an otName (= String to use as the name for object types), and an iotName
+ * (= String to use as the name for input object types). Eventually, data
+ * definitions also hold an ot (= the object type for the schema) and an iot
+ * (= the input object type for the schema).
  *
  * Either names or preferredName should exist.
  */