More control over importing behavior

[kbrandwijk]

Proposal (based on #13, #14 and #15):

Add optional parameter to importSchema:

rules? : {
   removeUnusedTypes?: boolean = true,
   importAllInterfaceImplementations?: boolean = false,
   importMissingTypes?: boolean = true,
   orderTypes?: boolean = false,
   strict?: boolean = true,
   validate?: boolean = false
}

Most are self-explanatory, strict: true would fail on missing schema files or missing imported types, otherwise silently ignored. validate: true would run the linter.

[schickling]

That looks good. Would be great if you could update your proposal to include default values.

[kbrandwijk]

@schickling Done.

[ccnixon]

Hey guys - any plans on taking a look at this in the near term? My use case:

I'm hoping to use graphql-s2s type inheritance in tandem with import statements but the validation step is failing. It would be great to be able to set a flag to bypass the validation step and and just compile the schema. Thanks!

[raeesaa]

I am having similar use case as @ccnixon. It would be great to have an option to bypass schema validation.

@kbrandwijk Any ETA for this issue?

[raeesaa]

@kbrandwijk Any updates on this?

[DavidStummer]

@kbrandwijk we would love this too

[ardatan]

Available in 1.0.0!