graphql-mesh

Patch Changes

• Updated dependencies [6e6fd4ab7]
• Updated dependencies [bcd9355ee]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @omnigraph/[email protected]
  • @graphql-mesh/[email protected]

Minor Changes

• eade5bb9f: New noDeduplication flag

  By default, JSON Schema handler tries to deduplicate similar JSON Schema types;

  Let's say we have the following JSON Schema;

  {
    "definitions": {
      "Book": {
        "type": "object",
        "title": "Book",
        "properties": {
          "title": {
            "type": "string"
          },
          "author": {
            "type": "string"
          },
          "price": {
            "type": "number"
          },
          "similarBooks": {
            "type": "array",
            "items": {
              "$ref": "#/definitions/SimilarBook"
            }
          }
        }
      },
      "SimilarBook": {
        "type": "object",
        "title": "Book",
        "properties": {
          "title": {
            "type": "string"
          },
          "author": {
            "type": "string"
          },
          "price": {
            "type": "number"
          },
          "similarBooks": {
            "type": "array",
            "items": {
              "$ref": "#/definitions/SimilarBook"
            }
          }
        }
      }
    }
  }
  

  And the result will be the following by default;

  type Book {
    title: String
    author: String
    price: Float
    similarBooks: [Book]
  }
  

  But if you set this flag true, it will not deduplicate similar JSON Schema types;

  type Book {
    title: String
    author: String
    price: Float
    similarBooks: [SimilarBook]
  }
  
  type SimilarBook {
    title: String
    author: String
    price: Float
    similarBooks: [SimilarBook]
  }
  

Patch Changes

• Updated dependencies [eade5bb9f]
• Updated dependencies [6e6fd4ab7]
• Updated dependencies [bcd9355ee]
  • [email protected]
  • @omnigraph/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [bcd9355ee]
  • @graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [eade5bb9f]
• Updated dependencies [6e6fd4ab7]
  • [email protected]
  • @omnigraph/[email protected]
  • @graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [6e6fd4ab7]
• Updated dependencies [bcd9355ee]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Minor Changes

• eade5bb9f: New noDeduplication flag

  By default, JSON Schema handler tries to deduplicate similar JSON Schema types;

  Let's say we have the following JSON Schema;

  {
    "definitions": {
      "Book": {
        "type": "object",
        "title": "Book",
        "properties": {
          "title": {
            "type": "string"
          },
          "author": {
            "type": "string"
          },
          "price": {
            "type": "number"
          },
          "similarBooks": {
            "type": "array",
            "items": {
              "$ref": "#/definitions/SimilarBook"
            }
          }
        }
      },
      "SimilarBook": {
        "type": "object",
        "title": "Book",
        "properties": {
          "title": {
            "type": "string"
          },
          "author": {
            "type": "string"
          },
          "price": {
            "type": "number"
          },
          "similarBooks": {
            "type": "array",
            "items": {
              "$ref": "#/definitions/SimilarBook"
            }
          }
        }
      }
    }
  }
  

  And the result will be the following by default;

  type Book {
    title: String
    author: String
    price: Float
    similarBooks: [Book]
  }
  

  But if you set this flag true, it will not deduplicate similar JSON Schema types;

  type Book {
    title: String
    author: String
    price: Float
    similarBooks: [SimilarBook]
  }
  
  type SimilarBook {
    title: String
    author: String
    price: Float
    similarBooks: [SimilarBook]
  }
  

Patch Changes

• Updated dependencies [eade5bb9f]
• Updated dependencies [6e6fd4ab7]
• Updated dependencies [bcd9355ee]
  • [email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [6e6fd4ab7]
• Updated dependencies [bcd9355ee]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Minor Changes

• bcd9355ee: Breaking change in merger API;

  Before a merger should return a GraphQLSchema, not it needs to return SubschemaConfig from @graphql-tools/delegate package.
  The idea is to prevent the schema from being wrap to reduce the execution complexity.
  Now if merger returns an executor, it will be used directly as an executor inside Envelop's pipeline.
  Also it can return transforms which will be applied during execution while schema transforms are applied on build time without any modification in the resolvers.

  If there are some root transforms, those are applied together with the source transforms on the execution level in case of a single source.

Patch Changes

• Updated dependencies [6e6fd4ab7]
• Updated dependencies [bcd9355ee]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [6e6fd4ab7]
• Updated dependencies [bcd9355ee]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [6e6fd4ab7]
• Updated dependencies [bcd9355ee]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [6e6fd4ab7]
• Updated dependencies [bcd9355ee]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [6e6fd4ab7]
• Updated dependencies [bcd9355ee]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [bcd9355ee]
  • @graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [6e6fd4ab7]
• Updated dependencies [bcd9355ee]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [6e6fd4ab7]
• Updated dependencies [bcd9355ee]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [bcd9355ee]
  • @graphql-mesh/[email protected]

Patch Changes

• bcd9355ee: If there is no comment in a field or table, do not create a description for the relevant fields and types
• Updated dependencies [6e6fd4ab7]
• Updated dependencies [bcd9355ee]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [6e6fd4ab7]
• Updated dependencies [bcd9355ee]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Minor Changes

• bcd9355ee: Breaking change in merger API;

  Before a merger should return a GraphQLSchema, not it needs to return SubschemaConfig from @graphql-tools/delegate package.
  The idea is to prevent the schema from being wrap to reduce the execution complexity.
  Now if merger returns an executor, it will be used directly as an executor inside Envelop's pipeline.
  Also it can return transforms which will be applied during execution while schema transforms are applied on build time without any modification in the resolvers.

  If there are some root transforms, those are applied together with the source transforms on the execution level in case of a single source.

Patch Changes

• @graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [6e6fd4ab7]
• Updated dependencies [bcd9355ee]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]