On this page

@omnigraph/openapi

Changelog for @omnigraph/openapi: every release with its changes and the pull requests behind them.

0.112.4

Patch Changes

  • Updated dependencies [d6ba079]:
    • @omnigraph/json-schema@0.112.4

0.112.3

Patch Changes

  • #9649 1a6dc08 Thanks @copilot-swe-agent! - Fix: honor loader-level queryStringOptions as fallback in @httpOperation directives

    Previously, when a queryStringOptions was configured at the loader (source) level for OpenAPI or JSON Schema subgraphs, the generated @httpOperation directives did not inherit that option unless every individual operation explicitly set its own queryStringOptions. This meant that loader-level query-string serialization config (e.g. allowDots, arrayFormat) was silently ignored at execution time.

    What changed

    In addExecutionDirectivesToComposer, each operation now falls back to the loader-level queryStringOptions when the operation itself does not define one:

    queryStringOptions: 'queryStringOptions' in operationConfig
      ? operationConfig.queryStringOptions
      : queryStringOptions // ← new: inherit from loader level

    This aligns with the documented contract where loader-level options apply globally to all operations.

    Usage example

    OpenAPI – queryStringOptions set once for all operations:

    // mesh.config.ts
    import { defineConfig } from '@graphql-mesh/compose-cli'
    import { loadOpenAPISubgraph } from '@omnigraph/openapi'
    
    export const composeConfig = defineConfig({
      subgraphs: [
        {
          sourceHandler: loadOpenAPISubgraph('MyApi', {
            source: './openapi.yaml',
            endpoint: 'https://api.example.com',
            // Applied to every operation that doesn't override it
            queryStringOptions: {
              allowDots: true, // serialize nested objects as a.b.c=1
              arrayFormat: 'repeat' // serialize arrays as a=1&a=2
            }
          })
        }
      ]
    })

    JSON Schema – same option at the loader level:

    import { loadGraphQLSchemaFromJSONSchemas } from '@omnigraph/json-schema';
    
    const schema = await loadGraphQLSchemaFromJSONSchemas('MyApi', {
      endpoint: 'https://api.example.com',
      queryStringOptions: {
        arrayFormat: 'brackets', // foo[]=1&foo[]=2
      },
      operations: [...],
    });

    Affected packages

    PackageChange
    @omnigraph/json-schemaCore fix in addExecutionDirectivesToComposer
    @omnigraph/openapiInherits fix via @omnigraph/json-schema

    Fixes #8760

  • Updated dependencies [c7f0f3f, c7f0f3f, 1a6dc08]:

    • @graphql-mesh/types@0.107.1
    • @omnigraph/json-schema@0.112.3
    • @graphql-mesh/utils@0.107.1
    • @graphql-mesh/fusion-composition@0.11.2

0.112.2

Patch Changes

  • Updated dependencies [5eab022]:
    • @omnigraph/json-schema@0.112.2

0.112.1

Patch Changes

  • 18cefe7 Thanks @ardatan! - Prefer application/x-www-form-urlencoded for request bodies when it is listed before JSON (OAuth token endpoints with oneOf + discriminator).

  • Updated dependencies [6f96258, c47a0c0, 5040fe9, 18cefe7, 6f96258]:

    • @omnigraph/json-schema@0.112.1
    • @graphql-mesh/fusion-composition@0.11.1
    • json-machete@0.97.8

0.112.0

Patch Changes

  • #9629 1849ec3 Thanks @copilot-swe-agent! - Stop mutating shared $ref parameter schemas when one operation marks the param required. Required args are collected per operation instead.

  • Updated dependencies [1849ec3, 1849ec3, 1849ec3, 1849ec3, ab73b38, 51b15f4]:

    • @omnigraph/json-schema@0.112.0
    • @graphql-mesh/types@0.107.0
    • @graphql-mesh/utils@0.107.0
    • @graphql-mesh/fusion-composition@0.11.0

0.111.0

Patch Changes

  • Updated dependencies [a7cbeef, cb846cb, 0f4ec4a, e148b13, 07c7b8e]:
    • @graphql-mesh/utils@0.106.0
    • @omnigraph/json-schema@0.111.0
    • @graphql-mesh/fusion-composition@0.10.0
    • @graphql-mesh/types@0.106.0

0.110.2

Patch Changes

  • Updated dependencies [f2f715f]:
    • @graphql-mesh/fusion-composition@0.9.2

0.110.1

Patch Changes

0.110.0

Patch Changes

  • Updated dependencies [b7def27]:
    • @graphql-mesh/types@0.105.0
    • @graphql-mesh/utils@0.105.0
    • @omnigraph/json-schema@0.110.0
    • @graphql-mesh/fusion-composition@0.9.0

0.109.54

Patch Changes

0.109.53

Patch Changes

0.109.52

Patch Changes

  • Updated dependencies [3aabd36, 9e23b1f]:
    • @omnigraph/json-schema@0.109.41
    • @graphql-mesh/fusion-composition@0.8.48

0.109.51

Patch Changes

0.109.50

Patch Changes

  • Updated dependencies [d62f684]:
    • @graphql-mesh/fusion-composition@0.8.46

0.109.49

Patch Changes

0.109.48

Patch Changes

  • Updated dependencies [d745894]:
    • @graphql-mesh/fusion-composition@0.8.44

0.109.47

Patch Changes

  • Updated dependencies [bc4b5d0]:
    • @graphql-mesh/fusion-composition@0.8.43

0.109.46

Patch Changes

  • Updated dependencies [95a2d10, 95a2d10, 95a2d10, 95a2d10]:
    • @graphql-mesh/fusion-composition@0.8.42
    • @graphql-mesh/types@0.104.26
    • @graphql-mesh/utils@0.104.34
    • @omnigraph/json-schema@0.109.38

0.109.45

Patch Changes

  • Updated dependencies [5c4b93b, 46d8eed]:
    • @graphql-mesh/fusion-composition@0.8.41
    • @graphql-mesh/utils@0.104.33
    • @omnigraph/json-schema@0.109.37

0.109.44

Patch Changes

  • Updated dependencies [94fbfbd]:
    • @graphql-mesh/string-interpolation@0.5.16
    • @graphql-mesh/utils@0.104.32
    • @omnigraph/json-schema@0.109.36
    • @graphql-mesh/fusion-composition@0.8.40

0.109.43

Patch Changes

  • Updated dependencies [339c32c]:
    • @graphql-mesh/string-interpolation@0.5.15
    • @graphql-mesh/utils@0.104.31
    • @omnigraph/json-schema@0.109.35
    • @graphql-mesh/fusion-composition@0.8.39

0.109.42

Patch Changes

  • Updated dependencies [3ad6a00, 3ad6a00]:
    • @graphql-mesh/string-interpolation@0.5.14
    • @omnigraph/json-schema@0.109.34
    • @graphql-mesh/utils@0.104.30
    • @graphql-mesh/fusion-composition@0.8.38

0.109.41

Patch Changes

  • Updated dependencies [13af2ff, 62c1082]:
    • @graphql-mesh/string-interpolation@0.5.13
    • json-machete@0.97.7
    • @graphql-mesh/utils@0.104.29
    • @omnigraph/json-schema@0.109.33
    • @graphql-mesh/fusion-composition@0.8.37

0.109.40

Patch Changes

  • Updated dependencies [300aea0, 300aea0, 300aea0, 300aea0]:
    • @graphql-mesh/fusion-composition@0.8.36
    • @graphql-mesh/types@0.104.25
    • @graphql-mesh/utils@0.104.28
    • @omnigraph/json-schema@0.109.32

0.109.39

Patch Changes

  • Updated dependencies [94c37cd, 17630d2]:
    • @graphql-mesh/fusion-composition@0.8.35

0.109.38

Patch Changes

  • Updated dependencies [2c80833, 2c80833, 2c80833, 2c80833]:
    • @graphql-mesh/fusion-composition@0.8.34
    • @graphql-mesh/types@0.104.24
    • @graphql-mesh/utils@0.104.27
    • @omnigraph/json-schema@0.109.31

0.109.37

Patch Changes

  • Updated dependencies [5d38d11]:
    • @graphql-mesh/string-interpolation@0.5.12
    • @graphql-mesh/utils@0.104.26
    • @omnigraph/json-schema@0.109.30
    • @graphql-mesh/fusion-composition@0.8.33

0.109.36

Patch Changes

  • Updated dependencies [4f81520, 04df502]:
    • @graphql-mesh/types@0.104.23
    • @graphql-mesh/fusion-composition@0.8.32
    • @graphql-mesh/utils@0.104.25
    • @omnigraph/json-schema@0.109.29

0.109.35

Patch Changes

  • Updated dependencies [457549e, 0664ddb]:
    • @graphql-mesh/fusion-composition@0.8.31
    • @omnigraph/json-schema@0.109.28

0.109.34

Patch Changes

0.109.33

Patch Changes

  • Updated dependencies [63b2a0b]:
    • @graphql-mesh/fusion-composition@0.8.29

0.109.32

Patch Changes

  • Updated dependencies [ec81ee4, 9d8b2b0]:
    • @omnigraph/json-schema@0.109.26

0.109.31

Patch Changes

  • Updated dependencies [d213cd9, d213cd9, d213cd9, ce55a45, d213cd9]:
    • @graphql-mesh/fusion-composition@0.8.28
    • @graphql-mesh/types@0.104.21
    • @graphql-mesh/utils@0.104.23
    • @omnigraph/json-schema@0.109.25

0.109.30

Patch Changes

0.109.29

Patch Changes

  • Updated dependencies [2410c44, 0028f3b]:
    • @omnigraph/json-schema@0.109.23
    • @graphql-mesh/string-interpolation@0.5.11
    • @graphql-mesh/utils@0.104.21
    • @graphql-mesh/fusion-composition@0.8.26

0.109.28

Patch Changes

0.109.27

Patch Changes

  • Updated dependencies [30e8e32]:
    • @graphql-mesh/string-interpolation@0.5.10
    • @graphql-mesh/utils@0.104.19
    • @omnigraph/json-schema@0.109.21
    • @graphql-mesh/fusion-composition@0.8.24

0.109.26

Patch Changes

  • #9089 c25d02e Thanks @ardatan! - - Support discriminator for OpenAPI documents with the definitions defined in definitions instead of components.schemas
    • Also while handling Inheritance and Polymorphism to look up for types in discriminator.mapping, if the pointers are not used, also check title to find the correct definition.
  • Updated dependencies [3878067, 4dea313, 0a2a0bc, d420cb2]:
    • @graphql-mesh/fusion-composition@0.8.23
    • @omnigraph/json-schema@0.109.20

0.109.25

Patch Changes

0.109.24

Patch Changes

  • Updated dependencies [3987b80, 3987b80, 3987b80]:
    • @graphql-mesh/types@0.104.17
    • @graphql-mesh/utils@0.104.17
    • @omnigraph/json-schema@0.109.18
    • @graphql-mesh/fusion-composition@0.8.21

0.109.23

Patch Changes

  • Updated dependencies [bb42d37, bb42d37]:
    • @graphql-mesh/types@0.104.16
    • @graphql-mesh/utils@0.104.16
    • @omnigraph/json-schema@0.109.17
    • @graphql-mesh/fusion-composition@0.8.20

0.109.22

Patch Changes

  • Updated dependencies [b077f20]:
    • @graphql-mesh/types@0.104.15
    • @graphql-mesh/utils@0.104.15
    • @omnigraph/json-schema@0.109.16
    • @graphql-mesh/fusion-composition@0.8.19

0.109.21

Patch Changes

  • Updated dependencies [1db3c6b]:
    • @graphql-mesh/types@0.104.14
    • @graphql-mesh/utils@0.104.14
    • @omnigraph/json-schema@0.109.15
    • @graphql-mesh/fusion-composition@0.8.18

0.109.20

Patch Changes

  • Updated dependencies [dfc6bc1, c880540, f7ce86c, dfc6bc1, dfc6bc1, dfc6bc1, 865b000]:
    • @graphql-mesh/fusion-composition@0.8.17
    • @graphql-mesh/string-interpolation@0.5.9
    • @graphql-mesh/types@0.104.13
    • @graphql-mesh/utils@0.104.13
    • @omnigraph/json-schema@0.109.14

0.109.19

Patch Changes

  • Updated dependencies [8c1456d, ffec6e7]:
    • @graphql-mesh/fusion-composition@0.8.16
    • @graphql-mesh/utils@0.104.12
    • @omnigraph/json-schema@0.109.13
    • @graphql-mesh/types@0.104.12

0.109.18

Patch Changes

  • Updated dependencies [d61faf0]:
    • @graphql-mesh/utils@0.104.11
    • @graphql-mesh/fusion-composition@0.8.15
    • @omnigraph/json-schema@0.109.12
    • @graphql-mesh/types@0.104.11

0.109.17

Patch Changes

  • Updated dependencies [7852ccd, 7852ccd]:
    • @graphql-mesh/utils@0.104.10
    • @graphql-mesh/fusion-composition@0.8.14
    • @omnigraph/json-schema@0.109.11
    • @graphql-mesh/types@0.104.10

0.109.16

Patch Changes

  • Updated dependencies [0c18fe1]:
    • @graphql-mesh/types@0.104.9
    • @graphql-mesh/utils@0.104.9
    • @omnigraph/json-schema@0.109.10
    • @graphql-mesh/fusion-composition@0.8.13

0.109.15

Patch Changes

  • Updated dependencies [fb6e935, fb6e935, fb6e935, 76df3d1]:
    • @graphql-mesh/types@0.104.8
    • @omnigraph/json-schema@0.109.9
    • @graphql-mesh/utils@0.104.8
    • @graphql-mesh/fusion-composition@0.8.12

0.109.14

Patch Changes

  • Updated dependencies [00dd66a, c37c23b]:
    • @graphql-mesh/fusion-composition@0.8.11
    • @graphql-mesh/types@0.104.7
    • @graphql-mesh/utils@0.104.7
    • @omnigraph/json-schema@0.109.8

0.109.13

Patch Changes

  • Updated dependencies [e2666bc]:
    • @graphql-mesh/utils@0.104.6
    • @graphql-mesh/fusion-composition@0.8.10
    • @omnigraph/json-schema@0.109.7
    • @graphql-mesh/types@0.104.6

0.109.12

Patch Changes

  • Updated dependencies [9d61d75]:
    • @graphql-mesh/utils@0.104.5
    • @graphql-mesh/fusion-composition@0.8.9
    • @omnigraph/json-schema@0.109.6
    • @graphql-mesh/types@0.104.5

0.109.11

Patch Changes

  • #8655 41757dd Thanks @arnaud! - The fix ensures that there is no correct or incorrect order of swaggers - whatever their order, schema loading and HATEOAS cross-referencing works reliably through coordinated batch processing with proper dependency resolution.

0.109.10

Patch Changes

  • Updated dependencies [6b4c546]:
    • @graphql-mesh/types@0.104.4
    • @graphql-mesh/utils@0.104.4
    • @omnigraph/json-schema@0.109.5
    • @graphql-mesh/fusion-composition@0.8.8

0.109.9

Patch Changes

  • #8641 17e3c35 Thanks @arnaud! - When there are two operations in the OAS; /products/ and /products/{id} Due to the bug in the logic, they conflict and the HATEOAS linking can choose the first one without any argument.

  • #8640 e254ba8 Thanks @arnaud! - fix(openapi): support 204 responses which have content keys with empty values

0.109.8

Patch Changes

  • Updated dependencies [74672d0]:
    • @graphql-mesh/fusion-composition@0.8.7

0.109.7

Patch Changes

0.109.6

Patch Changes

  • Updated dependencies [3528ddb]:
    • @graphql-mesh/fusion-composition@0.8.5

0.109.5

Patch Changes

  • Updated dependencies [3d33f2c, b432f1d]:
    • @graphql-mesh/fusion-composition@0.8.4

0.109.4

Patch Changes

  • Updated dependencies [cedadc5]:
    • @graphql-mesh/fusion-composition@0.8.3

0.109.3

Patch Changes

  • Updated dependencies [1b5d072]:
    • @graphql-mesh/utils@0.104.2
    • @graphql-mesh/fusion-composition@0.8.2
    • @omnigraph/json-schema@0.109.3
    • @graphql-mesh/types@0.104.2

0.109.2

Patch Changes

  • Updated dependencies []:
    • @omnigraph/json-schema@0.109.2

0.109.1

Patch Changes

  • Updated dependencies [b6c083c, f416982]:
    • @graphql-mesh/utils@0.104.1
    • @graphql-mesh/fusion-composition@0.8.1
    • @omnigraph/json-schema@0.109.1
    • @graphql-mesh/types@0.104.1

0.109.0

Patch Changes

  • Updated dependencies [4528794, 4528794]:
    • @graphql-mesh/utils@0.104.0
    • @graphql-mesh/fusion-composition@0.8.0
    • @omnigraph/json-schema@0.109.0
    • @graphql-mesh/types@0.104.0

0.108.25

Patch Changes

  • Updated dependencies [903124f]:
    • @graphql-mesh/utils@0.103.21
    • @graphql-mesh/fusion-composition@0.7.27
    • @omnigraph/json-schema@0.108.23
    • @graphql-mesh/types@0.103.21

0.108.24

Patch Changes

  • Updated dependencies [3f5e0a1]:
    • @graphql-mesh/utils@0.103.20
    • @graphql-mesh/fusion-composition@0.7.26
    • @omnigraph/json-schema@0.108.22
    • @graphql-mesh/types@0.103.20

0.108.23

Patch Changes

  • Updated dependencies [d9cf1d3]:
    • @graphql-mesh/types@0.103.19
    • @graphql-mesh/utils@0.103.19
    • @omnigraph/json-schema@0.108.21
    • @graphql-mesh/fusion-composition@0.7.25

0.108.22

Patch Changes

  • Updated dependencies [ab0863b, ab0863b]:
    • @graphql-mesh/utils@0.103.18
    • @omnigraph/json-schema@0.108.20
    • @graphql-mesh/fusion-composition@0.7.24
    • @graphql-mesh/types@0.103.18

0.108.21

Patch Changes

  • Updated dependencies [eee582a]:
    • @graphql-mesh/utils@0.103.17
    • @graphql-mesh/fusion-composition@0.7.23
    • @omnigraph/json-schema@0.108.19
    • @graphql-mesh/types@0.103.17

0.108.20

Patch Changes

  • Updated dependencies [b44f8b7]:
    • @omnigraph/json-schema@0.108.18
    • @graphql-mesh/types@0.103.16
    • @graphql-mesh/utils@0.103.16
    • @graphql-mesh/fusion-composition@0.7.22

0.108.19

Patch Changes

  • Updated dependencies [b5c05c4]:
    • @graphql-mesh/types@0.103.15
    • @graphql-mesh/utils@0.103.15
    • @omnigraph/json-schema@0.108.17
    • @graphql-mesh/fusion-composition@0.7.21

0.108.18

Patch Changes

  • Updated dependencies [fc44a1e]:
    • @graphql-mesh/types@0.103.14
    • @graphql-mesh/utils@0.103.14
    • @omnigraph/json-schema@0.108.16
    • @graphql-mesh/fusion-composition@0.7.20

0.108.17

Patch Changes

  • Updated dependencies [ce5e094, ce5e094, ce5e094, ce5e094, ce5e094]:
    • @graphql-mesh/cross-helpers@0.4.10
    • @graphql-mesh/fusion-composition@0.7.19
    • @graphql-mesh/types@0.103.13
    • @graphql-mesh/utils@0.103.13
    • @omnigraph/json-schema@0.108.15

0.108.16

Patch Changes

  • Updated dependencies []:
    • @omnigraph/json-schema@0.108.14

0.108.15

Patch Changes

  • #8289 c54e361 Thanks @ardatan! - New option selectQueryOrMutationField to decide which field belongs to which root type explicitly.

    import { defineConfig } from '@graphql-mesh/compose-cli'
    import loadGrpcSubgraph from '@omnigraph/grpc'
    
    export const composeConfig = defineConfig({
      subgraphs: [
        {
          sourceHandler: loadGrpcSubgraph('MyGrpcApi', {
            /** .. **/
    
            // Prefix to collect Query method default: list, get
            prefixQueryMethod: ['list', 'get'],
    
            // Select certain fields as Query or Mutation
            // This overrides `prefixQueryMethod`
            selectQueryOrMutationField: [
              {
                // You can use a pattern matching with *
                fieldName: '*RetrieveMovies',
                type: 'Query'
              },
              // Or you can use a specific field name
              // This will make the field GetMovie available as a Mutation
              // Because it would be Query because of `prefixQueryMethod`
              {
                fieldName: 'GetMovie',
                type: 'Mutation'
              }
            ]
          })
        }
      ]
    })
  • Updated dependencies [5180b06, c54e361, f1b5e8e, 78c202e]:

    • @graphql-mesh/utils@0.103.12
    • @graphql-mesh/types@0.103.12
    • @graphql-mesh/fusion-composition@0.7.18
    • @graphql-mesh/string-interpolation@0.5.8
    • @omnigraph/json-schema@0.108.13

0.108.14

Patch Changes

0.108.13

Patch Changes

  • Updated dependencies [3fc1f3e, 4011203]:
    • @graphql-mesh/types@0.103.11
    • @graphql-mesh/utils@0.103.11
    • @omnigraph/json-schema@0.108.11
    • @graphql-mesh/fusion-composition@0.7.17

0.108.12

Patch Changes

  • Updated dependencies [b750a41]:
    • @graphql-mesh/utils@0.103.10
    • @graphql-mesh/fusion-composition@0.7.16
    • @omnigraph/json-schema@0.108.10
    • @graphql-mesh/types@0.103.10

0.108.11

Patch Changes

  • Updated dependencies [10ba2c4]:
    • @graphql-mesh/utils@0.103.9
    • @graphql-mesh/fusion-composition@0.7.15
    • @omnigraph/json-schema@0.108.9
    • @graphql-mesh/types@0.103.9

0.108.10

Patch Changes

0.108.9

Patch Changes

0.108.8

Patch Changes

0.108.7

Patch Changes

0.108.6

Patch Changes

0.108.5

Patch Changes

  • #8007 9f9f6fe Thanks @ardatan! - DEBUG logs were accidentially written to the output, now it correctly prints logs to the logger not the output
  • Updated dependencies [9f9f6fe, 9f9f6fe]:
    • @omnigraph/json-schema@0.108.5
    • @graphql-mesh/utils@0.103.5
    • @graphql-mesh/types@0.103.5

0.108.4

Patch Changes

  • Updated dependencies [8fcfe3f]:
    • @graphql-mesh/types@0.103.4
    • @graphql-mesh/utils@0.103.4
    • @omnigraph/json-schema@0.108.4

0.108.3

Patch Changes

  • Updated dependencies [6360755]:
    • @graphql-mesh/utils@0.103.3
    • @omnigraph/json-schema@0.108.3
    • @graphql-mesh/types@0.103.3

0.108.2

Patch Changes

  • Updated dependencies [bfd8929]:
    • @graphql-mesh/utils@0.103.2
    • @omnigraph/json-schema@0.108.2
    • @graphql-mesh/types@0.103.2

0.108.1

Patch Changes

  • Updated dependencies [92d3ce1, 92d3ce1, 92d3ce1, 92d3ce1]:
    • @graphql-mesh/cross-helpers@0.4.8
    • @graphql-mesh/types@0.103.1
    • @graphql-mesh/utils@0.103.1
    • @omnigraph/json-schema@0.108.1

0.108.0

Patch Changes

  • Updated dependencies [0e49907, 9873b33]:
    • @graphql-mesh/utils@0.103.0
    • @omnigraph/json-schema@0.108.0
    • @graphql-mesh/types@0.103.0

0.107.8

Patch Changes

  • Updated dependencies [10dd636]:
    • @omnigraph/json-schema@0.107.8

0.107.7

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/types@0.102.13
    • @graphql-mesh/utils@0.102.13
    • @omnigraph/json-schema@0.107.7

0.107.6

Patch Changes

  • Updated dependencies [eee53b9, eee53b9]:
    • @graphql-mesh/utils@0.102.12
    • @omnigraph/json-schema@0.107.6
    • @graphql-mesh/types@0.102.12

0.107.5

Patch Changes

0.107.4

Patch Changes

0.107.3

Patch Changes

  • Updated dependencies [fad4d27]:
    • @graphql-mesh/utils@0.102.9
    • @omnigraph/json-schema@0.107.3
    • @graphql-mesh/types@0.102.9

0.107.2

Patch Changes

0.107.1

Patch Changes

0.107.0

Minor Changes

Patch Changes

  • Updated dependencies [c8b1309]:
    • @omnigraph/json-schema@0.107.0

0.106.9

Patch Changes

  • Updated dependencies [bf588d3]:
    • @graphql-mesh/utils@0.102.6
    • @omnigraph/json-schema@0.106.8
    • @graphql-mesh/types@0.102.6

0.106.8

Patch Changes

  • Updated dependencies [e0c0a94, fd245f2]:
    • @omnigraph/json-schema@0.106.7

0.106.7

Patch Changes

  • Updated dependencies [3bf14b3, b7f6ebf, 0a3e52c]:
    • @graphql-mesh/utils@0.102.5
    • @omnigraph/json-schema@0.106.6
    • @graphql-mesh/types@0.102.5

0.106.6

Patch Changes

  • Updated dependencies []:
    • @omnigraph/json-schema@0.106.5

0.106.5

Patch Changes

0.106.4

Patch Changes

0.106.3

Patch Changes

  • #7565 9118cf4 Thanks @ardatan! - Support different ref types in discriminator.mapping;

    All of the following ref formats are considered as valid;

    discriminator:
      mapping:
        A: '#/components/schemas/A'
        # or
        A: 'A'
        # or
        A: '../components/schemas/A'

0.106.2

Patch Changes

  • Updated dependencies [5d95aad]:
    • @graphql-mesh/utils@0.102.2
    • @omnigraph/json-schema@0.106.2
    • @graphql-mesh/types@0.102.2

0.106.1

Patch Changes

  • Updated dependencies [e49a7e6]:
    • @graphql-mesh/utils@0.102.1
    • @omnigraph/json-schema@0.106.1
    • @graphql-mesh/types@0.102.1

0.106.0

Patch Changes

  • Updated dependencies [13fa835, db41f96]:
    • @graphql-mesh/string-interpolation@0.5.6
    • @graphql-mesh/types@0.102.0
    • @graphql-mesh/utils@0.102.0
    • @omnigraph/json-schema@0.106.0

0.105.2

Patch Changes

0.105.1

Patch Changes

  • Updated dependencies []:
    • @omnigraph/json-schema@0.105.1

0.105.0

Patch Changes

0.104.0

Patch Changes

0.103.2

Patch Changes

  • Updated dependencies [a1bfc49]:
    • @graphql-mesh/types@0.99.7
    • @graphql-mesh/utils@0.99.7
    • @omnigraph/json-schema@0.103.2

0.103.1

Patch Changes

0.103.0

Minor Changes

  • #7443 8bccd9a Thanks @ardatan! - POSSIBLE BREAKING CHANGE WARNING: This change is breaking for OpenAPI schemas that have discriminator mapping. It fixes a bug when you have keys in the discriminator mapping that are invalid per GraphQL spec. Now in the artifacts @discriminator directive’s mapping argument is [String!]! instead of ObjMap. You should make sure both the consumer and the producer of the artifacts are updated to this version.

    discriminator:
      propertyName: petType
      mapping:
        'pet-cat': '#/components/schemas/Cat'
        'pet-dog': '#/components/schemas/Dog'

    This OpenAPI used to be translated into;

    @directive(mapping: { "pet-cat": "#/components/schemas/Cat", "pet-dog": "#/components/schemas/Dog" })

    But this is invalid in GraphQL spec, so now it’s translated into;

    @directive(mapping: [["pet-cat", "#/components/schemas/Cat"], ["pet-dog", "#/components/schemas/Dog"]])

Patch Changes

  • Updated dependencies [a4e53d9, 8bccd9a]:
    • @omnigraph/json-schema@0.103.0

0.102.7

Patch Changes

  • Updated dependencies [33c23e8]:
    • @graphql-mesh/utils@0.99.5
    • @omnigraph/json-schema@0.102.7
    • @graphql-mesh/types@0.99.5

0.102.6

Patch Changes

  • Updated dependencies [c4190a9]:
    • @omnigraph/json-schema@0.102.6

0.102.5

Patch Changes

  • Updated dependencies [597e790, 597e790]:
    • @graphql-mesh/utils@0.99.4
    • @omnigraph/json-schema@0.102.5
    • @graphql-mesh/types@0.99.4

0.102.4

Patch Changes

  • Updated dependencies [5e5dec5, 5e5dec5]:
    • @graphql-mesh/utils@0.99.3
    • @omnigraph/json-schema@0.102.4
    • @graphql-mesh/types@0.99.3

0.102.3

Patch Changes

  • Updated dependencies [ffe0346]:
    • @omnigraph/json-schema@0.102.3

0.102.2

Patch Changes

0.102.1

Patch Changes

0.102.0

Patch Changes

0.101.2

Patch Changes

  • Updated dependencies [a387451]:
    • @omnigraph/json-schema@0.101.2

0.101.1

Patch Changes

0.101.0

Minor Changes

  • #7145 7544594 Thanks @ardatan! - POTENTIAL BREAKING CHANGE:

    Now @httpOperation and @transport directive serializes headers as [string, string][] instead of stringified JSON.

    @httpOperation(
    -  operationSpecificHeaders: [["Authorization", "Bearer 123"], ["X-Api-Key", "123"]]
    +  operationSpecificHeaders: "{\"Authorization\": \"Bearer 123\", \"X-Api-Key\": \"123\"}"
    )
    @transport(
    -  headers: [["Authorization, "Bearer 123"], ["X-Api-Key", "123"]]
    +  headers: "{\"Authorization, \"Bearer 123\", \"X-Api-Key\": \"123\"}"
    )

    Also incorrect placement of @transport has been fixed to SCHEMA

    directive @transport on
    -  FIELD_DEFINITION
    +  SCHEMA

    There is still backwards compatibility but this might look like a breaking change for some users during schema validation.

Patch Changes

  • #7145 7544594 Thanks @Author, @User! - New Federation Composition Approach for the new Mesh v1 alpha; (If you are using Mesh v0 legacy, ignore this changelog)

    Now Mesh Compose produces a superset of Federated Supergraph.

    • Drop any options and implementation related to the old fusiongraph
      • The output is a valid supergraph that can be consumed by any Federation router. But if it is not Mesh Serve, the subgraph should still be served via Mesh Serve then consumed by that Federation router. If it is Mesh Serve, no additional server is needed because Mesh Serve already knows the additional directives etc of the transports
    • Compose the subgraphs using @theguild/federation-composition package
      • So benefit from the validation rules of Federation in Mesh Compose
    • Ability to consume existing federated subgraphs
      • Since the composition is now Federation, we can accept any federated subgraph
    • Implement Federation transform to transform any subgraph to a federated subgraph by adding Federation directives (v2 only) . This is on user’s own because they add the directives manually. And for __resolveReference, we use @merge directive to mark a root field as an entity resolver for Federation
    • Use additional @source directive to consume transforms on the subgraph execution (field renames etc)
    • Use additional @resolveTo directive to consume additional stitched resolvers
    • Use additional @transport directive to choose and configure a specific transport for subgraphs
    • Handle unsupported additional directives with another set of additional directives on Query for example directives on unions, schema definitions, enum values etc and then @extraUnionDirective added with missing directives for unions then on the runtime these directives are added back to the union for the subgraph execution of the transports.

    Basically Mesh Compose uses Federation spec for composition, validation and runtime BUT the output is a superset with these additional directives imported via @composeDirective;

    • @merge (Taken from Stitching Directives) If a custom entity resolver is defined for a root field like below, the gateway will pick it up as an entity resolver;
    type Query {
       fooById(id: ID!): Foo @merge(keyField: 'id', keyArg: 'id', subgraph: Foo)
    }
    • @resolveTo (Taken from v0) This allows to delegate to a field in any subgraph just like Schema Extensions in old Schema Stitching approach;
        extend type Book {
    
            @resolveTo(
              sourceName: "authors"
              sourceTypeName: "Query"
              sourceFieldName: "authors"
              keyField: "authorId"
              keysArg: "ids"
            )
        }
    • @source Taken from Fusion This allows us to know how the original definition is in the subgraph. If this directive exists, the runtime applies the transforms from Schema Stitching during the subgraph execution. This directive can exist in arguments, fields, types etc.
    type Query {
     @source(type: "MyUser") # This means `User` is actually `MyUser` in the actual subgraph
    }
    
    type User @source(name: "MyUser") {
      id: ID
      name: String
    }
    • @transport Taken from Fusion This allows us to choose a specific transport (rest, mysql, graphql-ws, graphql-http etc) for the subgraph execution with some configuration. In the runtime, the gateway loads the transports and passes the subgraph schema with annotations if needed to get an executor to execute queries against that subgraph.
    schema @transport(subgraph: "API", kind: "rest", location: "http://0.0.0.0:<api_port>") {
      query: Query
      mutation: Mutation
      subscription: Subscription
    }
    • @extraSchemaDefinitionDirective By default, it is not possible to add directives from subgraph to the supergraph but it is possible to do the same thing on types or fields. So we add this directive to Query for the directives we want to add to the schema. Then the runtime picks those per subgraph to put the directives back to their original places;
    type Query @extraSchemaDefinitionDirective(
      directives: {transport: [{subgraph: "petstore", kind: "rest", location: "http://0.0.0.0:<petstore_port>/api/v3"}]}
    )  {
    • @extraEnumValueDirective and @extraTypeDirective Same for enum values and unions etc that are not supported by the composition library

    Thanks to these directives, subgraphs can be published individually to Hive for example then the supergraph stored there can be handled by Mesh Gateway since the composition is the same. All the additions etc are done on the subgraph level. For the Fed gateways except Mesh Serve, subgraphs can be served individually by Mesh Serve again while they are consumed by any gw like Apollo Router Shareable is enabled by default for non-federated subgraphs

    Documentation PR has details for users; https://github.com/ardatan/graphql-mesh/pull/7109

  • Updated dependencies [7544594, f985978, 7544594, 7544594, ac77ce9]:

    • @omnigraph/json-schema@0.101.0
    • @graphql-mesh/utils@0.98.9
    • @graphql-mesh/types@0.98.9

0.100.14

Patch Changes

  • Updated dependencies []:
    • @omnigraph/json-schema@0.100.13

0.100.13

Patch Changes

0.100.12

Patch Changes

  • Updated dependencies [40d9235]:
    • @omnigraph/json-schema@0.100.11
    • @graphql-mesh/types@0.98.7
    • @graphql-mesh/utils@0.98.7

0.100.11

Patch Changes

  • Updated dependencies [882091b]:
    • @omnigraph/json-schema@0.100.10

0.100.10

Patch Changes

0.100.9

Patch Changes

  • Updated dependencies [c4d2249]:
    • @graphql-mesh/utils@0.98.5
    • @omnigraph/json-schema@0.100.8
    • @graphql-mesh/types@0.98.5

0.100.8

Patch Changes

  • Updated dependencies [5bfef52]:
    • @omnigraph/json-schema@0.100.7

0.100.7

Patch Changes

  • fb59244 Thanks @ardatan! - Update GraphQL Tools packages

  • Updated dependencies [fb59244]:

    • @omnigraph/json-schema@0.100.6
    • @graphql-mesh/types@0.98.4
    • @graphql-mesh/utils@0.98.4

0.100.6

Patch Changes

  • Updated dependencies [234d2f9, 234d2f9]:
    • @omnigraph/json-schema@0.100.5
    • json-machete@0.97.3

0.100.5

Patch Changes

  • c47b2aa Thanks @ardatan! - Bump GraphQL Tools versions

  • Updated dependencies [c47b2aa]:

    • @omnigraph/json-schema@0.100.4
    • @graphql-mesh/types@0.98.3
    • @graphql-mesh/utils@0.98.3

0.100.4

Patch Changes

  • Updated dependencies [f6af4b0]:
    • @omnigraph/json-schema@0.100.3

0.100.3

Patch Changes

0.100.2

Patch Changes

  • Updated dependencies [96dd11d]:
    • @omnigraph/json-schema@0.100.2
    • @graphql-mesh/cross-helpers@0.4.2
    • @graphql-mesh/types@0.98.2
    • @graphql-mesh/utils@0.98.2

0.100.1

Patch Changes

  • Updated dependencies [3d88cb8, 6044b7f]:
    • @graphql-mesh/string-interpolation@0.5.4
    • @graphql-mesh/types@0.98.1
    • @graphql-mesh/utils@0.98.1
    • @omnigraph/json-schema@0.100.1

0.100.0

Patch Changes

0.99.6

Patch Changes

  • Updated dependencies [52f74e7]:
    • @graphql-mesh/types@0.97.5
    • @graphql-mesh/utils@0.97.5
    • @omnigraph/json-schema@0.99.6

0.99.5

Patch Changes

  • Updated dependencies [e2fb7ed, e2fb7ed, ff33394]:
    • @graphql-mesh/utils@0.97.4
    • @graphql-mesh/types@0.97.4
    • @omnigraph/json-schema@0.99.5

0.99.4

Patch Changes

  • Updated dependencies [57f4a60]:
    • @graphql-mesh/types@0.97.3
    • @graphql-mesh/utils@0.97.3
    • @omnigraph/json-schema@0.99.4

0.99.3

Patch Changes

  • Updated dependencies [7a712ab]:
    • @graphql-mesh/types@0.97.2
    • @graphql-mesh/utils@0.97.2
    • @omnigraph/json-schema@0.99.3

0.99.2

Patch Changes

  • Updated dependencies [9667954]:
    • @omnigraph/json-schema@0.99.2

0.99.1

Patch Changes

  • Updated dependencies [dbaf72c]:
    • @graphql-mesh/types@0.97.1
    • @graphql-mesh/utils@0.97.1
    • @omnigraph/json-schema@0.99.1

0.99.0

Patch Changes

  • Updated dependencies [92dce67, 70b05a2]:
    • @graphql-mesh/types@0.97.0
    • @graphql-mesh/utils@0.97.0
    • @omnigraph/json-schema@0.99.0

0.98.2

Patch Changes

  • Updated dependencies [0f274ef]:
    • @graphql-mesh/utils@0.96.6
    • @omnigraph/json-schema@0.98.2
    • @graphql-mesh/types@0.96.6

0.98.1

Patch Changes

  • Updated dependencies [2138dea, 4b3ea1d]:
    • @omnigraph/json-schema@0.98.1
    • @graphql-mesh/types@0.96.5
    • @graphql-mesh/utils@0.96.5

0.98.0

Minor Changes

  • #6541 a7984e5 Thanks @ardatan! - BREAKING: Now getComposerFromSchema, addExecutionDirectivesToComposer, getUnionTypeComposers and getContainerTC needs `subgraphName` argument

Patch Changes

0.97.5

Patch Changes

  • Updated dependencies [ac26793]:
    • @graphql-mesh/types@0.96.3
    • @omnigraph/json-schema@0.97.4
    • @graphql-mesh/utils@0.96.3

0.97.4

Patch Changes

0.97.3

Patch Changes

  • Updated dependencies [87501f4]:
    • @omnigraph/json-schema@0.97.3

0.97.2

Patch Changes

  • Updated dependencies [d758afa, 4fac014]:
    • @graphql-mesh/types@0.96.2
    • @omnigraph/json-schema@0.97.2
    • @graphql-mesh/utils@0.96.2

0.97.1

Patch Changes

0.97.0

Patch Changes

  • Updated dependencies [7909bcb8c, 47a50aa6d]:
    • @omnigraph/json-schema@0.97.0
    • json-machete@0.97.0

0.96.0

Patch Changes

  • Updated dependencies [5c6a8f784]:
    • @omnigraph/json-schema@0.96.0
    • @graphql-mesh/types@0.96.0
    • json-machete@0.96.0
    • @graphql-mesh/utils@0.96.0

0.95.12

Patch Changes

  • Updated dependencies [9b8ba5d47, b4d38c55d]:
    • @omnigraph/json-schema@0.95.12
    • @graphql-mesh/string-interpolation@0.5.3
    • @graphql-mesh/utils@0.95.8
    • json-machete@0.95.8
    • @graphql-mesh/types@0.95.8

0.95.11

Patch Changes

  • Updated dependencies [7f467f522]:
    • @omnigraph/json-schema@0.95.11

0.95.10

Patch Changes

  • Updated dependencies [f55e946fc]:
    • @omnigraph/json-schema@0.95.10

0.95.9

Patch Changes

  • Updated dependencies [ae5e7c972]:
    • @omnigraph/json-schema@0.95.9

0.95.8

Patch Changes

  • a13969c77 Thanks @ardatan! - Support `deprecated` in OpenAPI and JSON Schemas

  • Updated dependencies [a13969c77]:

    • @omnigraph/json-schema@0.95.8
    • @graphql-mesh/types@0.95.7
    • json-machete@0.95.7
    • @graphql-mesh/utils@0.95.7

0.95.7

Patch Changes

  • Updated dependencies [8e1056cf9]:
    • @graphql-mesh/string-interpolation@0.5.2
    • @omnigraph/json-schema@0.95.7
    • @graphql-mesh/utils@0.95.6
    • json-machete@0.95.6
    • @graphql-mesh/types@0.95.6

0.95.6

Patch Changes

  • Updated dependencies [b8f16a42b, b8f16a42b]:
    • @graphql-mesh/cross-helpers@0.4.1
    • @graphql-mesh/types@0.95.5
    • json-machete@0.95.5
    • @omnigraph/json-schema@0.95.6
    • @graphql-mesh/utils@0.95.5

0.95.5

Patch Changes

  • Updated dependencies [625e5d787]:
    • @graphql-mesh/types@0.95.4
    • json-machete@0.95.4
    • @omnigraph/json-schema@0.95.5
    • @graphql-mesh/utils@0.95.4

0.95.4

Patch Changes

  • Updated dependencies [33ae7a89a]:
    • @graphql-mesh/types@0.95.3
    • @graphql-mesh/utils@0.95.3
    • json-machete@0.95.3
    • @omnigraph/json-schema@0.95.4

0.95.3

Patch Changes

  • #5643 94afd25a0 Thanks @cweckesser! - Fix issue regarding allOf operator that prevents overlapping sub-properties of objects provided to the operator from being merged
  • Updated dependencies [94afd25a0]:
    • @omnigraph/json-schema@0.95.3

0.95.2

Patch Changes

  • Updated dependencies [d8da4b282]:
    • @graphql-mesh/types@0.95.2
    • json-machete@0.95.2
    • @omnigraph/json-schema@0.95.2
    • @graphql-mesh/utils@0.95.2

0.95.1

Patch Changes

  • Updated dependencies [7cdc69e04]:
    • @graphql-mesh/types@0.95.1
    • json-machete@0.95.1
    • @omnigraph/json-schema@0.95.1
    • @graphql-mesh/utils@0.95.1

0.95.0

Patch Changes

  • Updated dependencies [bb50c4f94]:
    • @graphql-mesh/types@0.95.0
    • json-machete@0.95.0
    • @omnigraph/json-schema@0.95.0
    • @graphql-mesh/utils@0.95.0

0.94.10

Patch Changes

  • Updated dependencies [513512887, d1310cdff]:
    • @omnigraph/json-schema@0.94.9
    • @graphql-mesh/utils@0.94.6
    • json-machete@0.94.6
    • @graphql-mesh/types@0.94.6

0.94.9

Patch Changes

  • Updated dependencies [f11e9b307]:
    • @graphql-mesh/utils@0.94.5
    • json-machete@0.94.5
    • @omnigraph/json-schema@0.94.8
    • @graphql-mesh/types@0.94.5

0.94.8

Patch Changes

  • Updated dependencies [ff1678eea]:
    • @graphql-mesh/types@0.94.4
    • json-machete@0.94.4
    • @omnigraph/json-schema@0.94.7
    • @graphql-mesh/utils@0.94.4

0.94.7

Patch Changes

  • Updated dependencies [fba66c6fc]:
    • @graphql-mesh/string-interpolation@0.5.1
    • @omnigraph/json-schema@0.94.6
    • @graphql-mesh/utils@0.94.3
    • json-machete@0.94.3
    • @graphql-mesh/types@0.94.3

0.94.6

Patch Changes

  • Updated dependencies [d0d4917f4]:
    • @graphql-mesh/types@0.94.2
    • json-machete@0.94.2
    • @omnigraph/json-schema@0.94.5
    • @graphql-mesh/utils@0.94.2

0.94.5

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/types@0.94.1
    • json-machete@0.94.1
    • @omnigraph/json-schema@0.94.4
    • @graphql-mesh/utils@0.94.1

0.94.4

Patch Changes

  • Updated dependencies [298e1c180]:
    • @omnigraph/json-schema@0.94.3

0.94.3

Patch Changes

0.94.2

Patch Changes

0.94.1

Patch Changes

0.94.0

Minor Changes

Patch Changes

0.93.2

Patch Changes

  • #5441 5a6b66034 Thanks @devsergiy! - Fix handling reserved operations names (Query,Mutation) used as names of components Allow to use simple style of query params

  • #5452 8db1e91a8 Thanks @devsergiy! - skip extension fields in path object make comma style default for array param and undefined style

  • Updated dependencies [272c3f9b4, 5a6b66034, 0db5f9127]:

    • @omnigraph/json-schema@0.93.2

0.93.1

Patch Changes

1.0.0

Patch Changes

0.19.27

Patch Changes

0.19.26

Patch Changes

  • #5252 c90eb5ac6 Thanks @ardatan! - Make shared packages peer dependency

  • Updated dependencies [c90eb5ac6]:

    • @graphql-mesh/string-interpolation@0.4.3
    • @omnigraph/json-schema@0.38.24
    • @graphql-mesh/cross-helpers@0.3.4
    • json-machete@0.18.20
    • @graphql-mesh/types@0.91.12
    • @graphql-mesh/utils@0.43.20

0.19.25

Patch Changes

  • Updated dependencies [7e7096695, 7e7096695]:
    • @graphql-mesh/types@0.91.11
    • @omnigraph/json-schema@0.38.23
    • json-machete@0.18.19
    • @graphql-mesh/utils@0.43.19

0.19.24

Patch Changes

  • Updated dependencies [3f658a771, 3f658a771, 3f658a771]:
    • @omnigraph/json-schema@0.38.22
    • @graphql-mesh/utils@0.43.18
    • json-machete@0.18.18
    • @graphql-mesh/types@0.91.10

0.19.23

Patch Changes

  • Updated dependencies [a272fdbca]:
    • @graphql-mesh/types@0.91.9
    • json-machete@0.18.17
    • @omnigraph/json-schema@0.38.21
    • @graphql-mesh/utils@0.43.17

0.19.22

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/types@0.91.8
    • json-machete@0.18.16
    • @omnigraph/json-schema@0.38.20
    • @graphql-mesh/utils@0.43.16

0.19.21

Patch Changes

  • Updated dependencies [30d4c7cac]:
    • @omnigraph/json-schema@0.38.19

0.19.20

Patch Changes

  • Updated dependencies [accc99a6e]:
    • @omnigraph/json-schema@0.38.18

0.19.19

Patch Changes

  • Updated dependencies [fa2c010c1]:
    • @graphql-mesh/utils@0.43.15
    • json-machete@0.18.15
    • @omnigraph/json-schema@0.38.17
    • @graphql-mesh/types@0.91.7

0.19.18

Patch Changes

  • Updated dependencies [0b438c329, 0b438c329]:
    • @graphql-mesh/types@0.91.6
    • @graphql-mesh/utils@0.43.14
    • json-machete@0.18.14
    • @omnigraph/json-schema@0.38.16

0.19.17

Patch Changes

  • 6b4b0e16d Thanks @ardatan! - Do not count `servers` under operation as an HTTP method

0.19.16

Patch Changes

  • Updated dependencies [5c19f8d6f]:
    • @graphql-mesh/types@0.91.5
    • json-machete@0.18.13
    • @omnigraph/json-schema@0.38.15
    • @graphql-mesh/utils@0.43.13

0.19.15

Patch Changes

  • Updated dependencies [63ab17f0b]:
    • @graphql-mesh/types@0.91.4
    • json-machete@0.18.12
    • @omnigraph/json-schema@0.38.14
    • @graphql-mesh/utils@0.43.12

0.19.14

Patch Changes

  • Updated dependencies [bb58a5d9e]:
    • json-machete@0.18.11
    • @omnigraph/json-schema@0.38.13

0.19.13

Patch Changes

  • Updated dependencies [8c9c39cf5, 8c9c39cf5]:
    • @graphql-mesh/types@0.91.3
    • @graphql-mesh/utils@0.43.11
    • json-machete@0.18.10
    • @omnigraph/json-schema@0.38.12

0.19.12

Patch Changes

  • Updated dependencies [975715275, 989a47802]:
    • @graphql-mesh/cross-helpers@0.3.3
    • json-machete@0.18.9
    • @graphql-mesh/types@0.91.2
    • @omnigraph/json-schema@0.38.11
    • @graphql-mesh/utils@0.43.10

0.19.11

Patch Changes

  • Updated dependencies [d694ccc1f]:
    • @graphql-mesh/utils@0.43.9
    • json-machete@0.18.8
    • @omnigraph/json-schema@0.38.10
    • @graphql-mesh/types@0.91.1

0.19.10

Patch Changes

0.19.9

Patch Changes

  • Updated dependencies [2005d2b28, 2005d2b28, bcf29dfd0]:
    • @graphql-mesh/types@0.90.0
    • @graphql-mesh/utils@0.43.7
    • json-machete@0.18.6
    • @omnigraph/json-schema@0.38.8

0.19.8

Patch Changes

  • Updated dependencies [ed5843d8a, ed5843d8a]:
    • @graphql-mesh/types@0.89.5
    • @graphql-mesh/utils@0.43.6
    • json-machete@0.18.5
    • @omnigraph/json-schema@0.38.7

0.19.7

Patch Changes

0.19.6

Patch Changes

  • Updated dependencies [99f4c84e6, 99f4c84e6]:
    • @graphql-mesh/types@0.89.3
    • @graphql-mesh/utils@0.43.4
    • json-machete@0.18.3
    • @omnigraph/json-schema@0.38.5

0.19.5

Patch Changes

0.19.4

Patch Changes

0.19.3

Patch Changes

  • Updated dependencies [deb9912e0]:
    • @omnigraph/json-schema@0.38.3
    • @graphql-mesh/string-interpolation@0.4.1
    • @graphql-mesh/types@0.89.2
    • @graphql-mesh/utils@0.43.3
    • json-machete@0.18.2

0.19.2

Patch Changes

  • Updated dependencies [f1c2e20e5, f1c2e20e5]:
    • @graphql-mesh/types@0.89.1
    • @graphql-mesh/utils@0.43.2
    • json-machete@0.18.1
    • @omnigraph/json-schema@0.38.2

0.19.1

Patch Changes

  • Updated dependencies [d880342f6]:
    • @omnigraph/json-schema@0.38.1

0.19.0

Minor Changes

  • #4767 3edaa00ac Thanks @ardatan! - BREAKING - Neo4J handler’s url changed to endpoint to be consistent with other handlers BREAKING - Neo4J handler’s typeDefs changed to source to be consistent with other handlers BREAKING - OData handler’s url changed to endpoint to be consistent with other handlers BREAKING - OData handler’s metadata changed to source to be consistent with other handlers BREAKING - OpenAPI handler’s baseUrl changed to endpoint to be consistent with other handlers BREAKING - RAML handler’s baseUrl changed to endpoint to be consistent with other handlers BREAKING - RAML handler’s ramlFilePath changed to source to be consistent with other handlers

Patch Changes

  • Updated dependencies [3edaa00ac]:
    • json-machete@0.18.0
    • @omnigraph/json-schema@0.38.0
    • @graphql-mesh/types@0.89.0
    • @graphql-mesh/utils@0.43.1

0.18.0

Minor Changes

Patch Changes

0.17.11

Patch Changes

  • Updated dependencies [eba73c626, 979e8dcc6]:
    • @graphql-mesh/utils@0.42.9
    • @omnigraph/json-schema@0.36.11
    • json-machete@0.16.5
    • @graphql-mesh/types@0.87.1

0.17.10

Patch Changes

  • Updated dependencies [0d9771428, 686b3301b]:
    • @graphql-mesh/types@0.87.0
    • json-machete@0.16.4
    • @omnigraph/json-schema@0.36.10
    • @graphql-mesh/utils@0.42.8

0.17.9

Patch Changes

  • Updated dependencies [b390ecd1d]:
    • @omnigraph/json-schema@0.36.9

0.17.8

Patch Changes

  • #4825 3d8f23adb Thanks @ardatan! - Fixes on handling plural anyOf types

  • Updated dependencies [3d8f23adb]:

    • json-machete@0.16.3
    • @omnigraph/json-schema@0.36.8

0.17.7

Patch Changes

0.17.6

Patch Changes

0.17.5

Patch Changes

0.17.4

Patch Changes

  • Updated dependencies [d5f2d950e]:
    • json-machete@0.15.14
    • @graphql-mesh/utils@0.42.4
    • @omnigraph/json-schema@0.36.4
    • @graphql-mesh/types@0.85.5

0.17.3

Patch Changes

0.17.2

Patch Changes

0.17.1

Patch Changes

  • Updated dependencies [5c87cfc60, c72d904dc, 09c286994, c72d904dc]:
    • @graphql-mesh/string-interpolation@0.3.3
    • @omnigraph/json-schema@0.36.1
    • @graphql-mesh/types@0.85.2
    • json-machete@0.15.11
    • @graphql-mesh/utils@0.42.1

0.17.0

Minor Changes

  • #4708 1d61fbcec Thanks @ardatan! - BREAKING:
    • ”:” character is now sanitized as "" instead of “_COLON”
    • If a path starts with a variable like ”{” in an OAS operation, “by_” prefix is no longer added.

Patch Changes

  • Updated dependencies [398af2bf6, 1d61fbcec, a8d681274]:
    • @graphql-mesh/types@0.85.1
    • @graphql-mesh/utils@0.42.0
    • @omnigraph/json-schema@0.36.0
    • json-machete@0.15.10

0.16.10

Patch Changes

0.16.9

Patch Changes

  • Updated dependencies [6fb57d3ba, 814f2d516]:
    • @graphql-mesh/types@0.85.0
    • json-machete@0.15.9
    • @omnigraph/json-schema@0.35.9
    • @graphql-mesh/utils@0.41.22

0.16.8

Patch Changes

  • Updated dependencies [637e9e9d8]:
    • @graphql-mesh/types@0.84.10
    • json-machete@0.15.8
    • @omnigraph/json-schema@0.35.8
    • @graphql-mesh/utils@0.41.21

0.16.7

Patch Changes

  • Updated dependencies [48171a006, 48171a006, dd831a7d1]:
    • @omnigraph/json-schema@0.35.7
    • json-machete@0.15.7
    • @graphql-mesh/types@0.84.9
    • @graphql-mesh/utils@0.41.20

0.16.6

Patch Changes

  • Updated dependencies [5b44abcd2]:
    • @graphql-mesh/utils@0.41.19
    • json-machete@0.15.6
    • @omnigraph/json-schema@0.35.6
    • @graphql-mesh/types@0.84.8

0.16.5

Patch Changes

  • Updated dependencies [ffb301435, ffb301435]:
    • @graphql-mesh/types@0.84.7
    • @graphql-mesh/utils@0.41.18
    • json-machete@0.15.5
    • @omnigraph/json-schema@0.35.5

0.16.4

Patch Changes

  • Updated dependencies [31a64714a, 31a64714a]:
    • @graphql-mesh/types@0.84.6
    • @graphql-mesh/utils@0.41.17
    • json-machete@0.15.4
    • @omnigraph/json-schema@0.35.4

0.16.3

Patch Changes

  • Updated dependencies [88ab8f9ae]:
    • @graphql-mesh/utils@0.41.16
    • json-machete@0.15.3
    • @omnigraph/json-schema@0.35.3
    • @graphql-mesh/types@0.84.5

0.16.2

Patch Changes

  • Updated dependencies [186e37bcd]:
    • @graphql-mesh/utils@0.41.15
    • json-machete@0.15.2
    • @omnigraph/json-schema@0.35.2
    • @graphql-mesh/types@0.84.4

0.16.1

Patch Changes

  • Updated dependencies [93f4ed55d, d08ed0e77]:
    • @graphql-mesh/utils@0.41.14
    • @omnigraph/json-schema@0.35.1
    • json-machete@0.15.1
    • @graphql-mesh/types@0.84.3

0.16.0

Minor Changes

  • #4556 10f469e10 Thanks @ardatan! - If a component(response, requestBody, header or parameter) defined in OpenAPI schema, and its schema doesn’t have a title, use the component object’s title for that schema

    components:
      parameters:
        Foo:
          title: Foo
          in: query
          schema:
            # OAS Loader adds the following title
            # title: Foo_parameter
            type: string
            enum:
              - a
              - b

Patch Changes

  • #4556 10f469e10 Thanks @ardatan! - For const definitions, force {value}_const pattern for the generated titles instead of path based names

  • Updated dependencies [10f469e10, 10f469e10, 10f469e10]:

    • json-machete@0.15.0
    • @omnigraph/json-schema@0.35.0

0.15.4

Patch Changes

  • Updated dependencies [ff251e4c7]:
    • @graphql-mesh/types@0.84.2
    • json-machete@0.14.14
    • @omnigraph/json-schema@0.34.4
    • @graphql-mesh/utils@0.41.13

0.15.3

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/types@0.84.1
    • json-machete@0.14.13
    • @omnigraph/json-schema@0.34.3
    • @graphql-mesh/utils@0.41.12

0.15.2

Patch Changes

  • Updated dependencies [3cdb71eb7]:
    • @omnigraph/json-schema@0.34.2

0.15.1

Patch Changes

  • Updated dependencies [077e65c18, ee1cb6f76]:
    • @graphql-mesh/types@0.84.0
    • json-machete@0.14.12
    • @omnigraph/json-schema@0.34.1
    • @graphql-mesh/utils@0.41.11

0.15.0

Minor Changes

  • #4484 80013a3cd Thanks @ardatan! - If a union type has a single element, do not create that union type but use the element directly

Patch Changes

  • Updated dependencies [80013a3cd]:
    • @omnigraph/json-schema@0.34.0
    • @graphql-mesh/types@0.83.5
    • json-machete@0.14.11
    • @graphql-mesh/utils@0.41.10

0.14.11

Patch Changes

0.14.10

Patch Changes

0.14.9

Patch Changes

  • Updated dependencies [d84f81d94]:
    • @graphql-mesh/utils@0.41.7
    • json-machete@0.14.8
    • @omnigraph/json-schema@0.33.5
    • @graphql-mesh/types@0.83.2

0.14.8

Patch Changes

  • Updated dependencies [2a3753b5a, 2a3753b5a, 2a3753b5a]:
    • @graphql-mesh/utils@0.41.6
    • @omnigraph/json-schema@0.33.4
    • json-machete@0.14.7
    • @graphql-mesh/types@0.83.1

0.14.7

Patch Changes

  • Updated dependencies [a56ebcec5, 24afabece, 44b868196]:
    • @graphql-mesh/types@0.83.0
    • json-machete@0.14.6
    • @omnigraph/json-schema@0.33.3
    • @graphql-mesh/utils@0.41.5

0.14.6

Patch Changes

0.14.5

Patch Changes

  • Updated dependencies [b9bb80094, b9bb80094]:
    • @omnigraph/json-schema@0.33.1
    • @graphql-mesh/types@0.82.2
    • json-machete@0.14.4
    • @graphql-mesh/utils@0.41.3

0.14.4

Patch Changes

  • #4426 3571324cd Thanks @ardatan! - Respect original type for GraphQL Codegen TS definitions while generating a scalar type based on a RegExp pattern

  • Updated dependencies [3571324cd, 3571324cd]:

    • @omnigraph/json-schema@0.33.0
    • json-machete@0.14.3

0.14.3

Patch Changes

0.14.2

Patch Changes

0.14.1

Patch Changes

  • #4412 7e9482723 Thanks @ardatan! - Accept an array for “type” property in JSON Schema because it was broken and causing a bug that creates an invalid undefined scalar type.

    {
      "type": ["string", "number", "boolean", "integer", "array"]
    }
  • Updated dependencies [7e9482723, ca7994fad, ca7994fad]:

    • json-machete@0.14.1
    • @graphql-mesh/types@0.82.0
    • @omnigraph/json-schema@0.32.1
    • @graphql-mesh/utils@0.41.1

0.14.0

Minor Changes

  • #4378 5742f4598 Thanks @ardatan! - If an object type has a discriminator, it becomes an interface type and any other allOf references with that implements that interface

  • #4369 06904b29d Thanks @gilgardosh! - Support non-string link parameters

  • #4369 06904b29d Thanks @gilgardosh! - If you pass a function to operationHeaders, it takes the operation config as second parameter including path, method and other details about the request

  • #4376 3473a2686 Thanks @ardatan! - Support links on non-object fields

  • #4396 df37c40f4 Thanks @ardatan! - Drop webhook plugin and automatically handle webhooks. See the documentation for more information

  • #4369 06904b29d Thanks @gilgardosh! - Introduce “destructObject” in query stringify options to spread the parameter content into the query parameters in order to support OAS explode: true behavior with query parameters that are objects

  • #4375 0b3517539 Thanks @ardatan! - multipart/form-data and File Uploads support (type: string, format: binary)

    If there is type: string and format: binary definitions in a schema type definition, it is considered as File scalar type and resolved as WHATWG File object. When the request content-type is multipart/form-data, the handler creates a WHATWG FormData object and puts the input arguments in it.

  • #4379 7f0d02686 Thanks @ardatan! - Support readOnly and writeOnly. Now the fields flagged as writeOnly are not included in object types while writeOnly ones are not included in the input types, too.

Patch Changes

0.13.0

Minor Changes

  • #4364 32b3a63c2 Thanks @ardatan! - - Respect explode: true or explode: false in query parameter definitions in OAS
    • Introduce a new queryStringOptionsByParam option to define queryStringOptions for each query parameter

Patch Changes

  • Updated dependencies [32b3a63c2]:
    • @omnigraph/json-schema@0.31.0

0.12.0

Minor Changes

Patch Changes

  • Updated dependencies [b5c59ffce, be79b20a5, b5c59ffce]:
    • @graphql-mesh/utils@0.40.0
    • json-machete@0.13.2
    • @graphql-mesh/types@0.80.2
    • @omnigraph/json-schema@0.30.0

0.11.2

Patch Changes

  • Updated dependencies [cd13405f5]:
    • @omnigraph/json-schema@0.29.2

0.11.1

Patch Changes

  • Updated dependencies [f23e14eba]:
    • @graphql-mesh/utils@0.39.0
    • json-machete@0.13.1
    • @omnigraph/json-schema@0.29.1
    • @graphql-mesh/types@0.80.1

0.11.0

Minor Changes

  • #4342 ca6d6206b Thanks @gilgardosh! - ## Some improvements on OAS handling
    • If there are no parameters defined in OAS links, the handler exposes the arguments of the original operation.
    • If the name of the link definition is not valid for GraphQL, the handler sanitizes it.
  • #4327 f882aca38 Thanks @gilgardosh! - ## BREAKING CHANGES
    • Named types are no longer deduplicated automatically, so this might introduce new types on your side. Also the types with unknown content are always reflected as “JSON”/“Any” scalar type
    • noDeduplicate option has been dropped, because it is no longer needed.

Patch Changes

  • #4343 ab89f98cf Thanks @gilgardosh! - Add _ prefix if the type is Subscription to avoid conflict with the root “Subscription” type

0.10.0

Minor Changes

  • #4322 738335788 Thanks @ardatan! - POSSIBLE BREAKING CHANGE: Previously if the parameter name was not valid for GraphQL and sanitized like product-tag to product_tag, it was ignored. Now it has been fixed but this change might be a breaking change for you if the actual parameter schema is integer while it is represented as string today. This also fixes an issue with ignored default values.

Patch Changes

  • Updated dependencies [738335788]:
    • @omnigraph/json-schema@0.28.0

0.9.0

Minor Changes

  • #4235 b162269f7 Thanks @gilgardosh! - - Support “$request.query” and “$request.path” usages in OpenAPI runtime expressions

    • Fix Field not found error when an OpenAPI link refers to an operation which is not Mutation
    • Do not use AJV and check field names in the received object to resolve the type name for a union field
    • Fix queryParams which allows you to pass query parameters for all operations
    • Handle cookie paramters correctly defined in the OpenAPI document by trimming empty values
    • Respect the mime types defined in the OpenAPI document. Now it creates a union for each mime type defined in the document, and resolve it by the mime type.
    • Respect JSON examples given in the OpenAPI document correctly even if they are strings with JSON content.
    • Normalize(lowercase header names) and merge final operation headers correctly from different places operationHeaders from the bundle and configuration plus headers defined for that specific operation.
    • Do not ignore operationHeaders defined in the configuration even if there are some already defined in the bundle

    BREAKING CHANGES:

    • If a JSON Schema type cannot be represented in GraphQL (object without properties etc.), it will no longer use Any type but JSON type instead which is a scalar from graphql-scalars.

    • Due to the improvements in healJSONSchema some of types that are not named in the JSON Schema might be named in a different way. Please make sure the content of the types are correct and report us on GitHub if they are represented incorrectly.

    • UUID format is now represented as UUID scalar type which is a scalar from graphql-scalars.

    • HTTP Errors are now in a more descriptive way. If your consumer respects them strictly, they will probably need to update their implementation.

    {
      "url": "http://www.google.com/api",
      "method": "GET",
    - "status": 401,
    + "statusCode": 401,
    + "statusText": "Unauthorized",
    - "responseJson": {}
    + "responseBody": {}
    }
    • requestSchema and requestSample are no longer used for query parameters in GET operations, but instead we introduced new argTypeMap and queryParamArgMap to define schemas for query parameters.

    For JSON Schema Handler configuration, the following changes are NEEDED;

    - requestSample: { some_flag: true }
    + queryParamArgMap:
    +   some_flag: some_flag
    + argTypeMap:
    +   some_flag:
    +     type: boolean

    or just use the string interpolation;

    path: /mypath?some_flag={args.some_flag}
    • Query parameters no longer uses input, and they become an argument of that operation directly.

    In the generated GraphQL Schema;

    - someOp(input: SomeInput): OpResult
    - input SomeInput {
    -  some_flag: Boolean
    - }
    + someOp(some_flag: Boolean): OpResult
    • argTypeMap no longer takes GraphQL type names but instead it can take JSON Schema pointer or JSON Schema definition itself. New argTypeMap can configure any argument even if it is defined in the headers.
    argTypeMap:
    - some_flag: Boolean
    + some_flag:
    +   type: boolean

Patch Changes

  • Updated dependencies [b162269f7, 2ad667d96]:
    • @graphql-mesh/types@0.79.0
    • @graphql-mesh/utils@0.38.0
    • @omnigraph/json-schema@0.27.0
    • json-machete@0.12.0
    • @graphql-mesh/string-interpolation@0.3.2

0.8.2

Patch Changes

0.8.1

Patch Changes

0.8.0

Minor Changes

  • #4247 31fc25974 Thanks @ardatan! - Accept a code file for operationHeaders

    Now you can generate headers dynamically from the resolver data dynamically like below;

    operationHeaders: ./myOperationHeaders.ts

    And in myOperationHeaders.ts

    export default function myOperationHeaders({ context }: ResolverData) {
      const someToken = context.request.headers.get('some-token')
      const anotherToken = await someLogicThatReturnsAnotherToken(someToken)
      return {
        'x-bar-token': anotherToken
      }
    }

Patch Changes

0.7.11

Patch Changes

  • #4239 755d3d487 Thanks @ardatan! - - Set response type to “String” if the response content type is “text/*” defined in the OpenAPI document
    • Fix the issue when “allOf” or “anyOf” is used with an enum type and an object type
  • Updated dependencies [755d3d487, 669abf58f]:
    • @omnigraph/json-schema@0.25.0
    • json-machete@0.11.0

0.7.10

Patch Changes

  • #4237 02c018249 Thanks @ardatan! - - Respect pattern of number types
    • Dereference first-level circular dependencies properly in dereferenceObject
    • Do not make the schema single if there is one allOf or anyOf element but with properties
  • #4216 f95036a33 Thanks @ardatan! - Rewrite JSON Schema visitor and support circular dependencies in a better way

    Now visitJSONSchema takes two different visitor functions instead of enter and leave, previously we used to handle only leave.

    Also generateInterfaceFromSharedFields has been dropped for now because it wasn’t working as expected.

0.7.9

Patch Changes

  • 583da37fc: Fix an issue while concatenating query parameters for POST requests

    Before; http://localhost:3000/test?foo=barbaz=qux

    After; http://localhost:3000/test?foo=bar&barbaz=qux

0.7.8

Patch Changes

  • Updated dependencies [c88a34d82]
    • @omnigraph/json-schema@0.24.5
    • @graphql-mesh/types@0.78.5
    • @graphql-mesh/utils@0.37.6
    • json-machete@0.10.5

0.7.7

Patch Changes

  • Updated dependencies [30d046724]
    • @graphql-mesh/utils@0.37.5
    • json-machete@0.10.4
    • @omnigraph/json-schema@0.24.4
    • @graphql-mesh/types@0.78.4

0.7.6

Patch Changes

  • Updated dependencies [738e2f378]
    • @omnigraph/json-schema@0.24.3
    • @graphql-mesh/types@0.78.3
    • @graphql-mesh/utils@0.37.4
    • json-machete@0.10.3

0.7.5

Patch Changes

  • a2ef35c35: ** Use the new @whatwg-node/fetch package instead of cross-undici-fetch**

    cross-undici-fetch has been renamed to @whatwg-node-fetch. Now Mesh uses this new package.

    ** BREAKING: Drop serve.handlers in favor of the new plugin system **

    Now Mesh uses the new plugin system of GraphQL Yoga that uses WHATWG Fetch API instead of Node specific serve.handlers. That means you can use those plugins with any environment even if you are not using Node.js with mesh start.

    Please check our docs to see how you can migrate to the new usage. https://www.graphql-mesh.com/docs/guides/subscriptions-webhooks#handle-webhook-http-requests

  • Updated dependencies [bad0f40ab]

  • Updated dependencies [a2ef35c35]

    • @omnigraph/json-schema@0.24.2
    • json-machete@0.10.2
    • @graphql-mesh/types@0.78.2
    • @graphql-mesh/utils@0.37.3

0.7.4

Patch Changes

  • @graphql-mesh/types@0.78.1
  • @omnigraph/json-schema@0.24.1
  • @graphql-mesh/utils@0.37.2
  • json-machete@0.10.1

0.7.3

Patch Changes

  • Updated dependencies [eade5bb9f]
  • Updated dependencies [6e6fd4ab7]
  • Updated dependencies [bcd9355ee]
    • json-machete@0.10.0
    • @omnigraph/json-schema@0.24.0
    • @graphql-mesh/utils@0.37.1
    • @graphql-mesh/types@0.78.0

0.7.2

Patch Changes

  • Updated dependencies [66f5d0189]
  • Updated dependencies [0401c7617]
    • @graphql-mesh/types@0.77.1
    • @graphql-mesh/cross-helpers@0.2.0
    • @omnigraph/json-schema@0.23.0
    • @graphql-mesh/utils@0.37.0
    • json-machete@0.9.2

0.7.1

Patch Changes

  • Updated dependencies [b69746d2c]
  • Updated dependencies [12e1e5d72]
  • Updated dependencies [12e1e5d72]
  • Updated dependencies [12e1e5d72]
  • Updated dependencies [12e1e5d72]
    • @omnigraph/json-schema@0.22.0
    • @graphql-mesh/cross-helpers@0.1.7
    • @graphql-mesh/types@0.77.0
    • json-machete@0.9.1
    • @graphql-mesh/utils@0.36.1

0.7.0

Minor Changes

  • a0950ac6f: Breaking Change:

    • Now you can set a global customFetch instead of setting customFetch individually for each handler. customFetch configuration field for each handler will no longer work. And also customFetch needs to be the path of the code file that exports the function as default. moduleName#exportName is not supported for now.

    • While programmatically creating the handlers, now you also need fetchFn to be passed to the constructor;

    new GraphQLHandler({
      ...,
      fetchFn: myFetchFn,
    })
    • readFileOrUrl’s second config parameter is now required. Also this second parameter should take an object with cwd, importFn, fetch and logger. You can see the diff of handler’s codes as an example.

Patch Changes

  • Updated dependencies [19d06f6c9]
  • Updated dependencies [19d06f6c9]
  • Updated dependencies [a0950ac6f]
    • @graphql-mesh/utils@0.36.0
    • json-machete@0.9.0
    • @omnigraph/json-schema@0.21.0
    • @graphql-mesh/types@0.76.0

0.6.16

Patch Changes

  • Updated dependencies [d4754ad08]
  • Updated dependencies [2df026e90]
    • @graphql-mesh/types@0.75.0
    • @omnigraph/json-schema@0.20.7
    • @graphql-mesh/utils@0.35.7
    • json-machete@0.8.15

0.6.15

Patch Changes

  • Updated dependencies [ed9ba7f48]
    • @graphql-mesh/types@0.74.2
    • @graphql-mesh/utils@0.35.6
    • @omnigraph/json-schema@0.20.6
    • json-machete@0.8.14

0.6.14

Patch Changes

  • Updated dependencies [41cfb46b4]
    • @graphql-mesh/utils@0.35.5
    • json-machete@0.8.13
    • @omnigraph/json-schema@0.20.5
    • @graphql-mesh/types@0.74.1

0.6.13

Patch Changes

  • Updated dependencies [13b9b30f7]
    • @graphql-mesh/string-interpolation@0.3.0
    • @graphql-mesh/types@0.74.0
    • @omnigraph/json-schema@0.20.4
    • @graphql-mesh/utils@0.35.4
    • json-machete@0.8.12

0.6.12

Patch Changes

  • Updated dependencies [9733f490c]
    • @graphql-mesh/utils@0.35.3
    • json-machete@0.8.11
    • @omnigraph/json-schema@0.20.3
    • @graphql-mesh/types@0.73.3

0.6.11

Patch Changes

  • 3c0366d2c: - Support import.meta.env instead of process.env for browsers
    • Ponyfill util.inspect only if it is not Node env
  • Updated dependencies [3c0366d2c]
  • Updated dependencies [3c0366d2c]
    • @graphql-mesh/cross-helpers@0.1.6
    • json-machete@0.8.10
    • @omnigraph/json-schema@0.20.2
    • @graphql-mesh/utils@0.35.2
    • @graphql-mesh/types@0.73.2

0.6.10

Patch Changes

  • Updated dependencies [abe9fcc41]
    • @graphql-mesh/utils@0.35.1
    • json-machete@0.8.9
    • @omnigraph/json-schema@0.20.1
    • @graphql-mesh/types@0.73.1

0.6.9

Patch Changes

  • 974e703e2: Cleanup dependencies
  • Updated dependencies [974e703e2]
  • Updated dependencies [19a99c055]
  • Updated dependencies [974e703e2]
  • Updated dependencies [974e703e2]
  • Updated dependencies [893d526ab]
  • Updated dependencies [974e703e2]
    • json-machete@0.8.8
    • @omnigraph/json-schema@0.20.0
    • @graphql-mesh/string-interpolation@0.2.0
    • @graphql-mesh/types@0.73.0
    • @graphql-mesh/utils@0.35.0

0.6.8

Patch Changes

  • Updated dependencies [43eb3d2c2]
    • @graphql-mesh/utils@0.34.10
    • json-machete@0.8.7
    • @omnigraph/json-schema@0.19.8
    • @graphql-mesh/types@0.72.5

0.6.7

Patch Changes

  • Updated dependencies [55ad5ea44]
    • @graphql-mesh/utils@0.34.9
    • json-machete@0.8.6
    • @omnigraph/json-schema@0.19.7
    • @graphql-mesh/types@0.72.4

0.6.6

Patch Changes

  • Updated dependencies [31efa964e]
    • @graphql-mesh/utils@0.34.8
    • json-machete@0.8.5
    • @omnigraph/json-schema@0.19.6
    • @graphql-mesh/types@0.72.3

0.6.5

Patch Changes

  • json-machete@0.8.4
  • @graphql-mesh/utils@0.34.7
  • @graphql-mesh/types@0.72.2
  • @omnigraph/json-schema@0.19.5

0.6.4

Patch Changes

  • Updated dependencies [b9beacca2]
    • json-machete@0.8.3
    • @omnigraph/json-schema@0.19.4
    • @graphql-mesh/utils@0.34.6
    • @graphql-mesh/types@0.72.1

0.6.3

Patch Changes

  • Updated dependencies [fa2542468]
    • @graphql-mesh/types@0.72.0
    • @omnigraph/json-schema@0.19.3
    • @graphql-mesh/utils@0.34.5
    • json-machete@0.8.2

0.6.2

Patch Changes

  • Updated dependencies [ddbbec8a8]
    • @graphql-mesh/utils@0.34.4
    • json-machete@0.8.1
    • @omnigraph/json-schema@0.19.2
    • @graphql-mesh/types@0.71.4

0.6.1

Patch Changes

  • 2e9addd80: Bump cross-undici-fetch for Node 18 compat
  • Updated dependencies [2e9addd80]
  • Updated dependencies [2e9addd80]
    • json-machete@0.8.0
    • @omnigraph/json-schema@0.19.1
    • @graphql-mesh/utils@0.34.3
    • @graphql-mesh/types@0.71.3

0.6.0

Minor Changes

  • 2f395a4b2: feat(openapi): support empty values

Patch Changes

  • Updated dependencies [2f395a4b2]
    • @omnigraph/json-schema@0.19.0

0.5.2

Patch Changes

  • @graphql-mesh/types@0.71.2
  • @omnigraph/json-schema@0.18.2
  • @graphql-mesh/utils@0.34.2
  • json-machete@0.7.15

0.5.1

Patch Changes

  • 7856f92d3: Bump all packages
  • Updated dependencies [7856f92d3]
    • json-machete@0.7.14
    • @omnigraph/json-schema@0.18.1
    • @graphql-mesh/types@0.71.1
    • @graphql-mesh/utils@0.34.1

0.5.0

Minor Changes

  • 331b62637: feat(json-schema/openapi): support OpenAPI links and json pointer syntax in string interpolation

Patch Changes

  • 331b62637: fix(openapi): sanitize operationId before settings it as a GraphQL field name in the root type
  • 331b62637: fix(openapi): handle empty responses(204) correctly
  • Updated dependencies [331b62637]
  • Updated dependencies [331b62637]
  • Updated dependencies [f963b57ce]
  • Updated dependencies [0644f31f2]
  • Updated dependencies [331b62637]
  • Updated dependencies [331b62637]
  • Updated dependencies [331b62637]
  • Updated dependencies [331b62637]
  • Updated dependencies [331b62637]
    • json-machete@0.7.13
    • @omnigraph/json-schema@0.18.0
    • @graphql-mesh/types@0.71.0
    • @graphql-mesh/utils@0.34.0

0.4.9

Patch Changes

  • json-machete@0.7.12
  • @graphql-mesh/utils@0.33.6
  • @omnigraph/json-schema@0.17.26
  • @graphql-mesh/types@0.70.6

0.4.8

Patch Changes

  • @graphql-mesh/types@0.70.5
  • @omnigraph/json-schema@0.17.25
  • @graphql-mesh/utils@0.33.5
  • json-machete@0.7.11

0.4.7

Patch Changes

  • Updated dependencies [35a55e841]
    • json-machete@0.7.10
    • @omnigraph/json-schema@0.17.24
    • @graphql-mesh/types@0.70.4
    • @graphql-mesh/utils@0.33.4

0.4.6

Patch Changes

  • @graphql-mesh/types@0.70.3
  • @omnigraph/json-schema@0.17.23
  • @graphql-mesh/utils@0.33.3
  • json-machete@0.7.9

0.4.5

Patch Changes

  • Updated dependencies [d64c74b75]
    • json-machete@0.7.8
    • @omnigraph/json-schema@0.17.22

0.4.4

Patch Changes

  • Updated dependencies [b02f5b008]
  • Updated dependencies [114629e47]
    • @graphql-mesh/types@0.70.2
    • json-machete@0.7.7
    • @omnigraph/json-schema@0.17.21
    • @graphql-mesh/utils@0.33.2

0.4.3

Patch Changes

  • Updated dependencies [26e69dbe9]
    • @omnigraph/json-schema@0.17.20

0.4.2

Patch Changes

  • 2d5c6c72a: add Git repository link in package.json
  • Updated dependencies [2d5c6c72a]
    • json-machete@0.7.6
    • @omnigraph/json-schema@0.17.19
    • @graphql-mesh/types@0.70.1
    • @graphql-mesh/utils@0.33.1

0.4.1

Patch Changes

  • Updated dependencies [d567be7b5]
    • @graphql-mesh/types@0.70.0
    • @graphql-mesh/utils@0.33.0
    • @omnigraph/json-schema@0.17.18
    • json-machete@0.7.5

0.4.0

Minor Changes

  • f30dba61e: feat(openapi): add fallbackFormat

Patch Changes

  • Updated dependencies [f30dba61e]
    • @graphql-mesh/types@0.69.0
    • @omnigraph/json-schema@0.17.17
    • @graphql-mesh/utils@0.32.2
    • json-machete@0.7.4

0.3.28

Patch Changes

  • Updated dependencies [c53203723]
    • json-machete@0.7.3
    • @omnigraph/json-schema@0.17.16

0.3.27

Patch Changes

  • e67f6a621: fix(openapi): handle argTypeMap correctly
  • Updated dependencies [c6f0314ac]
    • json-machete@0.7.2
    • @omnigraph/json-schema@0.17.15

0.3.26

Patch Changes

  • 3448c3177: fix(openapi): sanitize dynamic argument names
    • @omnigraph/json-schema@0.17.14
    • @graphql-mesh/utils@0.32.1
    • json-machete@0.7.1

0.3.25

Patch Changes

  • Updated dependencies [67fb11706]
    • json-machete@0.7.0
    • @graphql-mesh/utils@0.32.0
    • @omnigraph/json-schema@0.17.13

0.3.24

Patch Changes

  • Updated dependencies [b2c537c2a]
    • @graphql-mesh/utils@0.31.0
    • json-machete@0.6.1
    • @omnigraph/json-schema@0.17.12

0.3.23

Patch Changes

  • Updated dependencies [b45dac0c0]
  • Updated dependencies [b45dac0c0]
    • json-machete@0.6.0
    • @omnigraph/json-schema@0.17.11

0.3.22

Patch Changes

  • @omnigraph/json-schema@0.17.10
  • @graphql-mesh/utils@0.30.2
  • json-machete@0.5.20

0.3.21

Patch Changes

  • @omnigraph/json-schema@0.17.9
  • @graphql-mesh/utils@0.30.1
  • json-machete@0.5.19

0.3.20

Patch Changes

  • Updated dependencies [01bac6bb5]
  • Updated dependencies [01bac6bb5]
    • @omnigraph/json-schema@0.17.8
    • @graphql-mesh/utils@0.30.0
    • json-machete@0.5.18

0.3.19

Patch Changes

  • Updated dependencies [268db0462]
    • @graphql-mesh/utils@0.29.0
    • json-machete@0.5.17
    • @omnigraph/json-schema@0.17.7

0.3.18

Patch Changes

  • @omnigraph/json-schema@0.17.6
  • @graphql-mesh/utils@0.28.5
  • json-machete@0.5.16

0.3.17

Patch Changes

  • @omnigraph/json-schema@0.17.5
  • @graphql-mesh/utils@0.28.4
  • json-machete@0.5.15

0.3.16

Patch Changes

  • Updated dependencies [f11d8b9c8]
    • @omnigraph/json-schema@0.17.4
    • @graphql-mesh/utils@0.28.3
    • json-machete@0.5.14

0.3.15

Patch Changes

  • Updated dependencies [fb876e99c]
    • @graphql-mesh/utils@0.28.2
    • @omnigraph/json-schema@0.17.3
    • json-machete@0.5.13

0.3.14

Patch Changes

  • @omnigraph/json-schema@0.17.2
  • @graphql-mesh/utils@0.28.1
  • json-machete@0.5.12

0.3.13

Patch Changes

  • 6f07de8fe: fix: do not import process from env
  • b481fbc39: enhance: add tslib to dependencies to reduce bundle size
  • Updated dependencies [6f07de8fe]
  • Updated dependencies [6f07de8fe]
  • Updated dependencies [b481fbc39]
    • @graphql-mesh/utils@0.28.0
    • @omnigraph/json-schema@0.17.1
    • json-machete@0.5.11

0.3.12

Patch Changes

  • c12e30ae5: fix(openapi): correct types for path params

0.3.11

Patch Changes

  • Updated dependencies [21de17a3d]
  • Updated dependencies [3f4bb09a9]
    • @omnigraph/json-schema@0.17.0
    • @graphql-mesh/utils@0.27.9
    • json-machete@0.5.10

0.3.10

Patch Changes

  • @omnigraph/json-schema@0.16.2
  • @graphql-mesh/utils@0.27.8
  • json-machete@0.5.9

0.3.9

Patch Changes

  • Updated dependencies [ca6bb5ff3]
  • Updated dependencies [ca6bb5ff3]
    • json-machete@0.5.8
    • @graphql-mesh/utils@0.27.7
    • @omnigraph/json-schema@0.16.1

0.3.8

Patch Changes

  • Updated dependencies [275f82b53]
    • @omnigraph/json-schema@0.16.0

0.3.7

Patch Changes

  • Updated dependencies [c84d9e95e]
    • @omnigraph/json-schema@0.15.1

0.3.6

Patch Changes

  • Updated dependencies [12256ec58]
  • Updated dependencies [e3f941db5]
    • @omnigraph/json-schema@0.15.0
    • @graphql-mesh/utils@0.27.6
    • json-machete@0.5.7

0.3.5

Patch Changes

  • Updated dependencies [1815865c3]
    • @omnigraph/json-schema@0.14.3
    • @graphql-mesh/utils@0.27.5
    • json-machete@0.5.6

0.3.4

Patch Changes

  • @omnigraph/json-schema@0.14.2
  • @graphql-mesh/utils@0.27.4
  • json-machete@0.5.5

0.3.3

Patch Changes

  • @omnigraph/json-schema@0.14.1
  • @graphql-mesh/utils@0.27.3
  • json-machete@0.5.4

0.3.2

Patch Changes

  • 0454c0f8a: fix(openapi): Interpolated required argument should be ID! not String!

0.3.1

Patch Changes

  • a00a88a97: fix(openapi): fix an issue when an arg is required

0.3.0

Minor Changes

  • 15e1f68c5: feat(json-schema): respect given samples in mocks transform

Patch Changes

  • Updated dependencies [c71b29004]
  • Updated dependencies [15e1f68c5]
    • @graphql-mesh/utils@0.27.2
    • @omnigraph/json-schema@0.14.0
    • json-machete@0.5.3

0.2.0

Minor Changes

  • 240ec7b38: feat(openapi): selectQueryOrMutationField flag to choose what field belongs to what root type

Patch Changes

  • Updated dependencies [fcbd12a35]
  • Updated dependencies [3a21004c9]
    • @graphql-mesh/utils@0.27.1
    • @omnigraph/json-schema@0.13.6
    • json-machete@0.5.2

0.1.7

Patch Changes

  • fb974bf73: fix(openapi): escape slashes in the content mimetype keys

0.1.6

Patch Changes

  • Updated dependencies [05ec30255]
    • @omnigraph/json-schema@0.13.5

0.1.5

Patch Changes

  • Updated dependencies [1c8827604]
    • json-machete@0.5.1
    • @omnigraph/json-schema@0.13.4

0.1.4

Patch Changes

  • Updated dependencies [49e9ca808]
  • Updated dependencies [49e9ca808]
    • json-machete@0.5.0
    • @omnigraph/json-schema@0.13.3

0.1.3

Patch Changes

  • Updated dependencies [900a01355]
    • @graphql-mesh/utils@0.27.0
    • json-machete@0.4.3
    • @omnigraph/json-schema@0.13.2

0.1.2

Patch Changes

  • @omnigraph/json-schema@0.13.1
  • @graphql-mesh/utils@0.26.4
  • json-machete@0.4.2

0.1.1

Patch Changes

  • Updated dependencies [a79268b3a]
    • @omnigraph/json-schema@0.13.0
    • @graphql-mesh/utils@0.26.3
    • json-machete@0.4.1

0.1.0

Minor Changes

  • 020431bdc: feat(json-schema/openapi/raml): respect error status codes

Patch Changes

  • Updated dependencies [020431bdc]
  • Updated dependencies [020431bdc]
    • json-machete@0.4.0
    • @omnigraph/json-schema@0.12.0
    • @graphql-mesh/utils@0.26.2

0.0.8

Patch Changes

  • 50684ddbf: fix(openapi): add lowercased method prefix
  • Updated dependencies [113091148]
  • Updated dependencies [6bb4cf673]
    • @graphql-mesh/utils@0.26.1
    • @omnigraph/json-schema@0.11.2
    • json-machete@0.3.7

0.0.7

Patch Changes

  • Updated dependencies [92d687133]
  • Updated dependencies [92d687133]
  • Updated dependencies [92d687133]
    • @omnigraph/json-schema@0.11.1
    • json-machete@0.3.6

0.0.6

Patch Changes

  • Updated dependencies [b69233517]
    • @omnigraph/json-schema@0.11.0

0.0.5

Patch Changes

  • Updated dependencies [6d76179e4]
    • @omnigraph/json-schema@0.10.0

0.0.4

Patch Changes

  • Updated dependencies [e30494c95]
    • @omnigraph/json-schema@0.9.0

0.0.3

Patch Changes

  • Updated dependencies [8e52fd06a]
  • Updated dependencies [1ab0aebbc]
  • Updated dependencies [56e2257fa]
  • Updated dependencies [56e2257fa]
    • json-machete@0.3.5
    • @omnigraph/json-schema@0.8.0
    • @graphql-mesh/utils@0.26.0

0.0.2

Patch Changes

  • Updated dependencies [2b876f2b8]
    • @graphql-mesh/utils@0.25.0
    • json-machete@0.3.4
    • @omnigraph/json-schema@0.7.4

0.0.1

Patch Changes

  • d907351c5: new OpenAPI Handler
  • Updated dependencies [d907351c5]
  • Updated dependencies [80eb8e92b]
  • Updated dependencies [d907351c5]
  • Updated dependencies [d907351c5]
    • json-machete@0.3.3
    • @omnigraph/json-schema@0.7.3
    • @graphql-mesh/utils@0.24.2