4.0.5 patch breaks @skip and @include directives in schema stitching

[herenickname]

After we have updated graphql-tools to 4.0.5:

@Skip and @include directives broke in schema stitching.

For example we had this query:

 games(order_by: {
  stats: {
   matches: desc
  }
 }) {
  id
  name
  shortName
  rawName: raw_name
  disabled
  stats @include(if: $requestStats) {
   id
   matchesCount: matches
   usersOnlineCount: users_online
   usersPlayed: users_played
  }
 }
}

We get this:

[yaacovCR]

Not having any directive support in addResolversToSchemas was protecting against default of no directives in mergeSchemas and adding back the default directives. Fix is within mergeSchemas to pass undefined instead of empty array when directive option is not enabled.

[yaacovCR]

Should be fixed in graphql-tools-fork. Let me know if you can if you have any issues.

[Grmiade]

Any news about this issue?

[Necmttn]

this was the solution for our case.

[kamilkisiela]

We recently released an alpha version of GraphQL Tools (#1308) that should fix the issue.

Please update graphql-tools to next or run:

npx match-version graphql-tools next

Let us know if it solves the problem, we're counting for your feedback! :)

[yaacovCR]

Rolled into #1306 .