Schema glob patterns not throwing errors

Describe the bug

When doing typescript codegen, using schema as a glob pattern swallows errors, while a list of schema files works.

To Reproduce Create 2 schemas, 1 with a syntax error and the other without. Using a glob schema will swallow the syntax error and individually listing each schema file with correctly throw the syntax error.

In the example, in codegen.yml, the glob route is running by default and swallows the error. Comment the glob way and uncomment out the list way, save the file, and it will correctly throw the error. https://codesandbox.io/s/peaceful-snowflake-epsdc?file=/codegen.yml

1. My GraphQL schema:

type Query {
  boop Boolean
}

type Query {
  beep: Boolean
}

1. My GraphQL operations: n/a

2. My codegen.yml config file:

# 1. Swallows errors and only outputs types for `two.gql`
schema: schemas/*.gql

# 2. Correctly throws syntax error for `one.gql`
#schema:
#  - schemas/one.gql
#  - schemas/two.gql


generates:
  types.ts:
    plugins:
      - typescript
      - typescript-operations

Expected behavior

Environment:

• OS: Linux
• @graphql-codegen/cli: 2.2.1
• @graphql-codegen/typescript: 2.2.4
• @graphql-codegen/typescript-operations: 2.1.8
• graphql: 15.7.2
• NodeJS: 14.8.1

Additional context

[ardatan]

This popped out after we started handling globs inside loaders instead of @graphql-tools/load level. I think the behavior of CodeFileLoader is being used in GraphQLFileLoader as well because in CodeFileLoader, we ignore the files which we cannot load with require or extract SDL with tag-pluck(otherwise you should need specifically define the files with GraphQL stuff). Also it is weird that we never notices in our bunch of unit tests. There are two things need to be done;

• Check existing tests and fix/update them to fail in this case
• Fix this weird behavior

[charlypoly]

@flippidippi, I created a reproduction repo with the latest versions of codegen packages: https://github.com/charlypoly/codegen-repros/tree/master/many-schema-files-swallow-errors

I cannot reproduce this issue; having an error in one.graphql does not get swallowed by the error in two.graphql.

Let us know if you still face this issue.