prisma-archive / graphql-transform-schema Goto Github PK

source/Schema/index.ts:14:43 - error TS2345: Argument of type 'import("/Users/jasonkuhrt/projects/personal/gql-examples/prisma-stitch/node_modules/@types/graphq...' is not assignable to parameter of type 'import("/Users/jasonkuhrt/projects/personal/gql-examples/prisma-stitch/node_modules/apollo-link/n...'.
  Types of property 'astNode' are incompatible.
    Type 'Maybe<SchemaDefinitionNode>' is not assignable to type 'SchemaDefinitionNode | undefined'.
      Type 'null' is not assignable to type 'SchemaDefinitionNode | undefined'.

14 const transformedSchema = transformSchema(schema, {})
                                             ~~~~~~

Guessing the issue here might be that my graphql-tools is not compatible with the current version of graphql-transform-schema.

The same field name might be used on two different root fields, so you need to be able to only filter out one of them.

Hi!

consider following schema:

type BoxImage implements ContentBox {
   id: String
   image: String
}

interface ContentBox{
  id: String
}

type Query {
  contentBoxById(id: String): ContentBox
}

Type BoxImage is valid return type for contentBoxById but it is removed from transformed schema:

transformSchema(remoteSchema, {
  Query: {
    '*': false,
     contentBoxById: true
  }
}

Many thanks and keep it up! :)

As mentioned in the schema transformation documentation, one can hide operations in a transformSchema call by setting boolean values against desired queries/mutations like so:

// Example below is from the documentation

const schema = ... // this is the GraphQLSchema instance implementing the SDL from above
const transformedSchema = transformSchema(schema, {
  Query: {
    'allUsers': false   // hide `allUsers` field on `Query` type
  },
  Mutation: {
    'deleteUser': false // hide `deleteUser` field on `Mutation` type
  }
})

However, there may be situations where you'd want to conditionally hide one query/mutation or another. This functionality could be provided by functions, but I'm still on the fence how, especially when functions are used to modify arguments before they hit a resolve (so how could you tell a "hiding" function from a "modifying" function?). I still feel this could be a good feature.

• This issue is caused by graphql-transform-schema not using the peer dependency, so the version of graphql is misaligned when the peer is using an updated version of graphql. Need to resolve to peer dependency or make it a clear version requirement

See apollographql/apollo-server#643 for more details.

The dependency lodash was updated from 4.17.10 to 4.17.11.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

lodash is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴