On this page

@omnigraph/soap

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

0.110.1

Patch Changes

  • Updated dependencies [c7f0f3f, c7f0f3f]:
    • @graphql-mesh/types@0.107.1
    • @graphql-mesh/utils@0.107.1
    • @graphql-mesh/transport-soap@0.13.1

0.110.0

Patch Changes

  • Updated dependencies [ab73b38, 51b15f4]:
    • @graphql-mesh/types@0.107.0
    • @graphql-mesh/utils@0.107.0
    • @graphql-mesh/transport-soap@0.13.0

0.109.0

Patch Changes

0.108.1

Patch Changes

0.108.0

Patch Changes

0.107.47

Patch Changes

  • #9465 eece882 Thanks @zcag! - dependencies updates:

  • #9527 59a2e76 Thanks @dependabot! - dependencies updates:

  • #9530 6282a71 Thanks @dependabot! - dependencies updates:

  • #9547 b28d9ec Thanks @dependabot! - dependencies updates:

  • #9558 cfa9cd9 Thanks @dependabot! - dependencies updates:

  • #9467 db6d772 Thanks @zcag! - Resolve nested <wsdl:import> and <xsd:import> against the importing document’s location, not against a fixed cwd. Lets the loader follow multi-file WSDLs whose schemas span more than one directory (e.g. TMForum MTOP, OASIS) without flattening them first.

    Also handles the common <xsd:schema> wrapper pattern — a schema element with no targetNamespace whose only purpose is to bring an external schema into <wsdl:types> via <xsd:import>. This is widely used and valid per the XML Schema spec; the previous code crashed dereferencing targetNamespace.

    fetchWSDL now uses readFileOrUrl, matching fetchXSD, so WSDL imports work uniformly with both http(s): URLs and filesystem paths.

    The new optional baseUrl parameter on loadWSDL lets callers tell the loader where the document came from. When omitted, the legacy cwd-based behaviour is preserved unchanged.

  • #9465 eece882 Thanks @zcag! - Correct SOAP envelope generation for WSDLs with multiple XSD namespaces and <soap:header> bindings, and fix array serialization.

    Three issues are addressed together because they all surface on the same class of WSDL (one operation, multiple XSD schemas, header binding, array-typed parts):

    • XML namespace — every body element used to be qualified with the WSDL bindingNamespace. Now each element gets the namespace of the schema where it is declared, so types that come from a different XSD render under their own prefix.
    • <soap:header> binding — message parts the WSDL routes to <soap:Header> were being placed inside <soap:Body>. The loader now records header parts on the @soap directive and the executor splits them into <soap:Header> at request time.
    • Arrays — array-valued args were iterated with for..in, producing numeric child elements (<prefix:0>, <prefix:1>). They now serialize as repeated sibling elements.

    The new namespace-aware path activates only when the schema was built by the updated loader (it now exposes a typeNamespaceMap on schema.extensions and a per-arg namespace map on the @soap directive) and bodyAlias is not configured. Schemas built by older loader versions, and any usage that sets bodyAlias, continue to use the legacy code path unchanged. For single-namespace WSDLs without bodyAlias the new path falls back to the same body prefix the legacy path used, preserving byte-for-byte compatibility (covered by a regression test against tempconvert.wsdl).

  • Updated dependencies [eece882, 6282a71, b28d9ec, eece882, eece882, 59a2e76, 6282a71, b28d9ec, cfa9cd9, eece882, 59a2e76, 6282a71, b28d9ec, 1b0e3c4, eece882, 444fbbe, 6282a71, 2c347d5, b28d9ec, 1b0e3c4, cd30910, eece882, 4c56adc]:

    • @graphql-mesh/cross-helpers@0.4.15
    • @graphql-mesh/string-interpolation@0.5.18
    • @graphql-mesh/transport-soap@0.10.47
    • @graphql-mesh/types@0.104.30
    • @graphql-mesh/utils@0.104.38

0.107.46

Patch Changes

0.107.45

Patch Changes

0.107.44

Patch Changes

0.107.43

Patch Changes

0.107.42

Patch Changes

  • #9406 af31a59 Thanks @dependabot! - dependencies updates:

  • #9414 136ebb7 Thanks @zcag! - Fix anonymous inline complex type name collisions when multiple parent types define same-named inline fields

  • #9420 9944c5b Thanks @zcag! - fix(soap): skip xs:any wildcard namespace tokens (##other, ##any, etc.) instead of treating them as namespace URIs

  • #9416 4c604bf Thanks @zcag! - Add missing xs:anySimpleType to built-in XSD type map, mapping it to GraphQLString

  • #9415 f86dfe1 Thanks @zcag! - Fix crash when empty complex type used in repeated element (getTypePlural called on raw GraphQLJSON scalar)

  • #9422 a4b4cfd Thanks @zcag! - fix(soap): resolve element type aliases that forward-reference types from later schemas

  • #9421 46d314a Thanks @zcag! - fix(soap): sanitize XSD type and field names containing illegal GraphQL characters (dots, hyphens, etc.)

  • #9417 5065c46 Thanks @zcag! - Fix GraphQL type name collisions when multiple embedded schemas share the same namespace alias (e.g. tns)

  • Updated dependencies [af31a59, af31a59, af31a59, af31a59]:

    • @graphql-mesh/cross-helpers@0.4.13
    • @graphql-mesh/transport-soap@0.10.42
    • @graphql-mesh/types@0.104.27
    • @graphql-mesh/utils@0.104.35

0.107.41

Patch Changes

0.107.40

Patch Changes

0.107.39

Patch Changes

  • Updated dependencies [95a2d10, 95a2d10]:
    • @graphql-mesh/types@0.104.26
    • @graphql-mesh/utils@0.104.34
    • @graphql-mesh/transport-soap@0.10.39

0.107.38

Patch Changes

0.107.37

Patch Changes

  • Updated dependencies [94fbfbd]:
    • @graphql-mesh/string-interpolation@0.5.16
    • @graphql-mesh/utils@0.104.32
    • @graphql-mesh/transport-soap@0.10.37

0.107.36

Patch Changes

  • Updated dependencies [339c32c]:
    • @graphql-mesh/string-interpolation@0.5.15
    • @graphql-mesh/utils@0.104.31
    • @graphql-mesh/transport-soap@0.10.36

0.107.35

Patch Changes

  • Updated dependencies [3ad6a00]:
    • @graphql-mesh/string-interpolation@0.5.14
    • @graphql-mesh/utils@0.104.30
    • @graphql-mesh/transport-soap@0.10.35

0.107.34

Patch Changes

0.107.33

Patch Changes

  • Updated dependencies [300aea0, 300aea0]:
    • @graphql-mesh/types@0.104.25
    • @graphql-mesh/utils@0.104.28
    • @graphql-mesh/transport-soap@0.10.33

0.107.32

Patch Changes

0.107.31

Patch Changes

0.107.30

Patch Changes

0.107.29

Patch Changes

  • Updated dependencies [4f81520]:
    • @graphql-mesh/types@0.104.23
    • @graphql-mesh/utils@0.104.25
    • @graphql-mesh/transport-soap@0.10.29

0.107.28

Patch Changes

0.107.27

Patch Changes

0.107.26

Patch Changes

0.107.25

Patch Changes

  • Updated dependencies [d213cd9, d213cd9]:
    • @graphql-mesh/types@0.104.21
    • @graphql-mesh/utils@0.104.23
    • @graphql-mesh/transport-soap@0.10.25

0.107.24

Patch Changes

0.107.23

Patch Changes

0.107.22

Patch Changes

0.107.21

Patch Changes

  • Updated dependencies [30e8e32]:
    • @graphql-mesh/string-interpolation@0.5.10
    • @graphql-mesh/utils@0.104.19
    • @graphql-mesh/transport-soap@0.10.21

0.107.20

Patch Changes

0.107.19

Patch Changes

0.107.18

Patch Changes

  • Updated dependencies [3987b80, 3987b80]:
    • @graphql-mesh/types@0.104.17
    • @graphql-mesh/utils@0.104.17
    • @graphql-mesh/transport-soap@0.10.18

0.107.17

Patch Changes

  • Updated dependencies [bb42d37, bb42d37]:
    • @graphql-mesh/types@0.104.16
    • @graphql-mesh/utils@0.104.16
    • @graphql-mesh/transport-soap@0.10.17

0.107.16

Patch Changes

  • Updated dependencies [b077f20]:
    • @graphql-mesh/types@0.104.15
    • @graphql-mesh/utils@0.104.15
    • @graphql-mesh/transport-soap@0.10.16

0.107.15

Patch Changes

  • Updated dependencies [1db3c6b]:
    • @graphql-mesh/types@0.104.14
    • @graphql-mesh/utils@0.104.14
    • @graphql-mesh/transport-soap@0.10.15

0.107.14

Patch Changes

0.107.13

Patch Changes

  • Updated dependencies [ffec6e7]:
    • @graphql-mesh/utils@0.104.12
    • @graphql-mesh/transport-soap@0.10.13
    • @graphql-mesh/types@0.104.12

0.107.12

Patch Changes

  • Updated dependencies [d61faf0]:
    • @graphql-mesh/utils@0.104.11
    • @graphql-mesh/transport-soap@0.10.12
    • @graphql-mesh/types@0.104.11

0.107.11

Patch Changes

  • Updated dependencies [7852ccd, 7852ccd]:
    • @graphql-mesh/utils@0.104.10
    • @graphql-mesh/transport-soap@0.10.11
    • @graphql-mesh/types@0.104.10

0.107.10

Patch Changes

  • Updated dependencies [0c18fe1]:
    • @graphql-mesh/types@0.104.9
    • @graphql-mesh/utils@0.104.9
    • @graphql-mesh/transport-soap@0.10.10

0.107.9

Patch Changes

  • Updated dependencies [fb6e935, fb6e935, fb6e935]:
    • @graphql-mesh/types@0.104.8
    • @graphql-mesh/utils@0.104.8
    • @graphql-mesh/transport-soap@0.10.9

0.107.8

Patch Changes

  • Updated dependencies [c37c23b]:
    • @graphql-mesh/types@0.104.7
    • @graphql-mesh/utils@0.104.7
    • @graphql-mesh/transport-soap@0.10.8

0.107.7

Patch Changes

  • Updated dependencies [e2666bc]:
    • @graphql-mesh/utils@0.104.6
    • @graphql-mesh/transport-soap@0.10.7
    • @graphql-mesh/types@0.104.6

0.107.6

Patch Changes

  • Updated dependencies [9d61d75]:
    • @graphql-mesh/utils@0.104.5
    • @graphql-mesh/transport-soap@0.10.6
    • @graphql-mesh/types@0.104.5

0.107.5

Patch Changes

  • Updated dependencies [6b4c546]:
    • @graphql-mesh/types@0.104.4
    • @graphql-mesh/utils@0.104.4
    • @graphql-mesh/transport-soap@0.10.5

0.107.4

Patch Changes

0.107.3

Patch Changes

  • Updated dependencies [1b5d072]:
    • @graphql-mesh/utils@0.104.2
    • @graphql-mesh/transport-soap@0.10.3
    • @graphql-mesh/types@0.104.2

0.107.2

Patch Changes

  • Updated dependencies [1577309]:
    • @graphql-mesh/transport-soap@0.10.2

0.107.1

Patch Changes

  • Updated dependencies [b6c083c, f416982]:
    • @graphql-mesh/utils@0.104.1
    • @graphql-mesh/transport-soap@0.10.1
    • @graphql-mesh/types@0.104.1

0.107.0

Patch Changes

  • Updated dependencies [4528794, 4528794]:
    • @graphql-mesh/utils@0.104.0
    • @graphql-mesh/transport-soap@0.10.0
    • @graphql-mesh/types@0.104.0

0.106.2

Patch Changes

  • Updated dependencies [903124f]:
    • @graphql-mesh/utils@0.103.21
    • @graphql-mesh/transport-soap@0.9.2
    • @graphql-mesh/types@0.103.21

0.106.1

Patch Changes

0.106.0

Minor Changes

  • #8414 d9cf1d3 Thanks @ardatan! - Auto detection of SOAP version to decide SOAP namespace; For SOAP 1.1, it is set to http://schemas.xmlsoap.org/soap/envelope/ and for SOAP 1.2, it is set to http://www.w3.org/2003/05/soap-envelope.

    If you want to use a custom namespace, you can set it like below;

    import { defineConfig } from '@graphql-mesh/compose-cli'
    import { loadSOAPSubgraph } from '@omnigraph/soap'
    
    export const composeConfig = defineConfig({
      subgraphs: [
        {
          sourceHandler: loadSOAPSubgraph('CountryInfo', {
            source:
              'http://webservices.oorsprong.org/websamples.countryinfo/CountryInfoService.wso?WSDL',
            soapNamespace: 'http://foo.com/schemas/soap/envelope'
          })
        }
      ]
    })

Patch Changes

  • Updated dependencies [d9cf1d3]:
    • @graphql-mesh/transport-soap@0.9.0
    • @graphql-mesh/types@0.103.19
    • @graphql-mesh/utils@0.103.19

0.105.18

Patch Changes

0.105.17

Patch Changes

  • Updated dependencies [eee582a]:
    • @graphql-mesh/utils@0.103.17
    • @graphql-mesh/transport-soap@0.8.17
    • @graphql-mesh/types@0.103.17

0.105.16

Patch Changes

  • Updated dependencies [b44f8b7]:
    • @graphql-mesh/types@0.103.16
    • @graphql-mesh/utils@0.103.16
    • @graphql-mesh/transport-soap@0.8.16

0.105.15

Patch Changes

  • Updated dependencies [b5c05c4]:
    • @graphql-mesh/types@0.103.15
    • @graphql-mesh/utils@0.103.15
    • @graphql-mesh/transport-soap@0.8.15

0.105.14

Patch Changes

  • Updated dependencies [fc44a1e]:
    • @graphql-mesh/types@0.103.14
    • @graphql-mesh/utils@0.103.14
    • @graphql-mesh/transport-soap@0.8.14

0.105.13

Patch Changes

0.105.12

Patch Changes

  • #8282 40274c3 Thanks @ardatan! - Some SOAP API endpoints need SOAPAction HTTP header that points to the action path defined in the WSDL. This fixes that issue for those endpoints. Learn more about SOAPAction header
  • Updated dependencies [5180b06, c54e361, 40274c3, 78c202e]:
    • @graphql-mesh/utils@0.103.12
    • @graphql-mesh/types@0.103.12
    • @graphql-mesh/transport-soap@0.8.12
    • @graphql-mesh/string-interpolation@0.5.8

0.105.11

Patch Changes

  • #8196 3fc1f3e Thanks @ardatan! - dependencies updates:

  • #8196 3fc1f3e Thanks @ardatan! - - You can now choose the name of the alias you want to use for SOAP body;

    import { defineConfig } from '@graphql-mesh/compose-cli'
    
    export const composeConfig = defineConfig({
      sources: [
        {
          sourceHandler: loadSOAPSubgraph('CountryInfo', {
            source:
              'http://webservices.oorsprong.org/websamples.countryinfo/CountryInfoService.wso?WSDL',
            bodyAlias: 'my-body'
          })
        }
      ]
    })
    • Then it will generate a body like below by using the alias;
    <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:my-body="http://foo.com/">
       <soap:Body>
          <my-body:Foo>
              <my-body:Bar>baz</my-body:Bar>
          </my-body:Foo>
       </soap:Body>
    </soap:Envelope>

    If you want to add SOAP headers to the request body like below;

    <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:header="http://foo.com/">
       <soap:Header>
          <header:MyHeader>
             <header:UserName>user</header:UserName>
             <header:Password>password</header:Password>
          </header:MyHeader>
       </soap:Header>

    You can add the headers to the configuration like below;

    import { defineConfig } from '@graphql-mesh/compose-cli'
    import { loadSOAPSubgraph } from '@omnigraph/soap'
    
    export const composeConfig = defineConfig({
      subgraphs: [
        {
          sourceHandler: loadSOAPSubgraph('CountryInfo', {
            source:
              'http://webservices.oorsprong.org/websamples.countryinfo/CountryInfoService.wso?WSDL',
            soapHeaders: {
              alias: 'header',
              namespace: 'http://foo.com',
              headers: {
                MyHeader: {
                  UserName: 'user',
                  Password: 'password'
                }
              }
            }
          })
        }
      ]
    })
  • Updated dependencies [3fc1f3e, 4011203]:

    • @graphql-mesh/transport-soap@0.8.11
    • @graphql-mesh/types@0.103.11
    • @graphql-mesh/utils@0.103.11

0.105.10

Patch Changes

  • Updated dependencies [b750a41]:
    • @graphql-mesh/utils@0.103.10
    • @graphql-mesh/transport-soap@0.8.10
    • @graphql-mesh/types@0.103.10

0.105.9

Patch Changes

  • Updated dependencies [10ba2c4]:
    • @graphql-mesh/utils@0.103.9
    • @graphql-mesh/transport-soap@0.8.9
    • @graphql-mesh/types@0.103.9

0.105.8

Patch Changes

  • Updated dependencies [93fb364]:
    • @graphql-mesh/utils@0.103.8
    • @graphql-mesh/transport-soap@0.8.8
    • @graphql-mesh/types@0.103.8

0.105.7

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/types@0.103.7
    • @graphql-mesh/utils@0.103.7
    • @graphql-mesh/transport-soap@0.8.7

0.105.6

Patch Changes

0.105.5

Patch Changes

  • Updated dependencies [9f9f6fe]:
    • @graphql-mesh/utils@0.103.5
    • @graphql-mesh/transport-soap@0.8.5
    • @graphql-mesh/types@0.103.5

0.105.4

Patch Changes

  • Updated dependencies [8fcfe3f]:
    • @graphql-mesh/types@0.103.4
    • @graphql-mesh/utils@0.103.4
    • @graphql-mesh/transport-soap@0.8.4

0.105.3

Patch Changes

  • Updated dependencies [6360755]:
    • @graphql-mesh/utils@0.103.3
    • @graphql-mesh/transport-soap@0.8.3
    • @graphql-mesh/types@0.103.3

0.105.2

Patch Changes

  • Updated dependencies [bfd8929]:
    • @graphql-mesh/utils@0.103.2
    • @graphql-mesh/transport-soap@0.8.2
    • @graphql-mesh/types@0.103.2

0.105.1

Patch Changes

0.105.0

Patch Changes

  • Updated dependencies [0e49907, 9873b33]:
    • @graphql-mesh/utils@0.103.0
    • @graphql-mesh/transport-soap@0.8.0
    • @graphql-mesh/types@0.103.0

0.104.14

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/types@0.102.13
    • @graphql-mesh/utils@0.102.13
    • @graphql-mesh/transport-soap@0.7.14

0.104.13

Patch Changes

0.104.12

Patch Changes

  • Updated dependencies [de41fc2, de41fc2]:
    • @graphql-mesh/types@0.102.11
    • @graphql-mesh/utils@0.102.11
    • @graphql-mesh/transport-soap@0.7.12

0.104.11

Patch Changes

  • Updated dependencies [997b81c, 997b81c]:
    • @graphql-mesh/types@0.102.10
    • @graphql-mesh/utils@0.102.10
    • @graphql-mesh/transport-soap@0.7.11

0.104.10

Patch Changes

  • Updated dependencies [fad4d27]:
    • @graphql-mesh/utils@0.102.9
    • @graphql-mesh/transport-soap@0.7.10
    • @graphql-mesh/types@0.102.9

0.104.9

Patch Changes

  • Updated dependencies [518c42c, 518c42c]:
    • @graphql-mesh/types@0.102.8
    • @graphql-mesh/utils@0.102.8
    • @graphql-mesh/transport-soap@0.7.9

0.104.8

Patch Changes

0.104.7

Patch Changes

  • 900e84c Thanks @enisdenjo! - Bump potential CVE dependencies

  • Updated dependencies [bf588d3, 900e84c]:

    • @graphql-mesh/utils@0.102.6
    • @graphql-mesh/transport-soap@0.7.7
    • @graphql-mesh/types@0.102.6

0.104.6

Patch Changes

  • Updated dependencies [3bf14b3, b7f6ebf, 0a3e52c]:
    • @graphql-mesh/utils@0.102.5
    • @graphql-mesh/transport-soap@0.7.6
    • @graphql-mesh/types@0.102.5

0.104.5

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/transport-soap@0.7.5

0.104.4

Patch Changes

  • Updated dependencies [edbc074, edbc074]:
    • @graphql-mesh/types@0.102.4
    • @graphql-mesh/utils@0.102.4
    • @graphql-mesh/transport-soap@0.7.4

0.104.3

Patch Changes

  • Updated dependencies [14ec31f, 14ec31f]:
    • @graphql-mesh/types@0.102.3
    • @graphql-mesh/utils@0.102.3
    • @graphql-mesh/transport-soap@0.7.3

0.104.2

Patch Changes

  • Updated dependencies [5d95aad]:
    • @graphql-mesh/utils@0.102.2
    • @graphql-mesh/transport-soap@0.7.2
    • @graphql-mesh/types@0.102.2

0.104.1

Patch Changes

  • Updated dependencies [e49a7e6, 60bfc22]:
    • @graphql-mesh/utils@0.102.1
    • @graphql-mesh/transport-soap@0.7.1
    • @graphql-mesh/types@0.102.1

0.104.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
    • @graphql-mesh/transport-soap@0.7.0

0.103.2

Patch Changes

0.103.1

Patch Changes

  • Updated dependencies [67e1062]:
    • @graphql-mesh/transport-soap@0.6.1

0.103.0

Patch Changes

0.102.0

Patch Changes

0.101.7

Patch Changes

  • Updated dependencies [a1bfc49]:
    • @graphql-mesh/types@0.99.7
    • @graphql-mesh/utils@0.99.7
    • @graphql-mesh/transport-soap@0.4.7

0.101.6

Patch Changes

  • Updated dependencies [6c67e77, 6c67e77, 6c67e77]:
    • @graphql-mesh/types@0.99.6
    • @graphql-mesh/utils@0.99.6
    • @graphql-mesh/transport-soap@0.4.6

0.101.5

Patch Changes

  • Updated dependencies [33c23e8]:
    • @graphql-mesh/utils@0.99.5
    • @graphql-mesh/transport-soap@0.4.5
    • @graphql-mesh/types@0.99.5

0.101.4

Patch Changes

  • Updated dependencies [597e790, 597e790]:
    • @graphql-mesh/utils@0.99.4
    • @graphql-mesh/transport-soap@0.4.4
    • @graphql-mesh/types@0.99.4

0.101.3

Patch Changes

  • Updated dependencies [5e5dec5, 5e5dec5]:
    • @graphql-mesh/utils@0.99.3
    • @graphql-mesh/transport-soap@0.4.3
    • @graphql-mesh/types@0.99.3

0.101.2

Patch Changes

  • Updated dependencies [b01f3ea, 0bdc18d, 4bc495c, 4bc495c]:
    • @graphql-mesh/string-interpolation@0.5.5
    • @graphql-mesh/types@0.99.2
    • @graphql-mesh/utils@0.99.2
    • @graphql-mesh/transport-soap@0.4.2

0.101.1

Patch Changes

  • Updated dependencies [7800514, 7800514]:
    • @graphql-mesh/types@0.99.1
    • @graphql-mesh/utils@0.99.1
    • @graphql-mesh/transport-soap@0.4.1

0.101.0

Patch Changes

  • Updated dependencies [a8e3f00, a8e3f00]:
    • @graphql-mesh/utils@0.99.0
    • @graphql-mesh/transport-soap@0.4.0
    • @graphql-mesh/types@0.99.0

0.100.2

Patch Changes

  • da0c516 Thanks @ardatan! - Fix the inverted nullability generation

    If SOAP has nillable: true, the generated type was non-nullable, and now it has been fixed to be nullable as expected.

0.100.1

Patch Changes

0.100.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

0.99.4

Patch Changes

0.99.3

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/types@0.98.7
    • @graphql-mesh/utils@0.98.7
    • @graphql-mesh/transport-soap@0.2.7

0.99.2

Patch Changes

0.99.1

Patch Changes

  • Updated dependencies [c4d2249]:
    • @graphql-mesh/utils@0.98.5
    • @graphql-mesh/types@0.98.5
    • @graphql-mesh/transport-soap@0.2.5

0.99.0

Minor Changes

Patch Changes

  • #6992 bd5cea3 Thanks @ardatan! - Support documents without any prefixes on W3 definitions like xs etc.

    WSDL definitions might not have any prefix for W3 definitions as in here;

    <xs:schema />

    Unlike this one;

    <schema />

    Both are supported, previously it was throwing while looking for a namespace prefix for W3. Now it considers W3 to be the default/global namespace if there is no explicit prefix for it in the document.

    <wsdl:definitions xmlns:xsd="http://www.w3.org/2001/XMLSchema" />
  • #6992 bd5cea3 Thanks @ardatan! - Support new numeric types; integer, negativeInteger, nonNegativeInteger, nonPositiveInteger and positiveInteger as scalar types

    See all the numeric types in SOAP; https://www.w3schools.com/xml/schema_dtypes_numeric.asp

  • #6992 bd5cea3 Thanks @ardatan! - Support extended enum types, before it was supporting string only but it might be other types of enums which are not string. In GraphQL, there is not such a thing like Enum<T> so all enums are just enums.

0.98.4

Patch Changes

  • Updated dependencies [fb59244]:
    • @graphql-mesh/types@0.98.4
    • @graphql-mesh/utils@0.98.4
    • @graphql-mesh/transport-soap@0.2.4

0.98.3

Patch Changes

  • Updated dependencies [c47b2aa]:
    • @graphql-mesh/types@0.98.3
    • @graphql-mesh/utils@0.98.3
    • @graphql-mesh/transport-soap@0.2.3

0.98.2

Patch Changes

  • 96dd11d Thanks @ardatan! - Bump GraphQL Tools versions

  • Updated dependencies [96dd11d]:

    • @graphql-mesh/transport-soap@0.2.2
    • @graphql-mesh/cross-helpers@0.4.2
    • @graphql-mesh/types@0.98.2
    • @graphql-mesh/utils@0.98.2

0.98.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
    • @graphql-mesh/transport-soap@0.2.1

0.98.0

Patch Changes

  • Updated dependencies [2fcadce, 2fcadce, 6399add, 6399add]:
    • @graphql-mesh/types@0.98.0
    • @graphql-mesh/utils@0.98.0
    • @graphql-mesh/transport-soap@0.2.0

0.97.5

Patch Changes

  • Updated dependencies [52f74e7]:
    • @graphql-mesh/types@0.97.5
    • @graphql-mesh/utils@0.97.5
    • @graphql-mesh/transport-soap@0.1.5

0.97.4

Patch Changes

  • Updated dependencies [e2fb7ed, e2fb7ed, ff33394]:
    • @graphql-mesh/utils@0.97.4
    • @graphql-mesh/types@0.97.4
    • @graphql-mesh/transport-soap@0.1.4

0.97.3

Patch Changes

  • Updated dependencies [57f4a60]:
    • @graphql-mesh/types@0.97.3
    • @graphql-mesh/utils@0.97.3
    • @graphql-mesh/transport-soap@0.1.3

0.97.2

Patch Changes

  • Updated dependencies [7a712ab]:
    • @graphql-mesh/types@0.97.2
    • @graphql-mesh/utils@0.97.2
    • @graphql-mesh/transport-soap@0.1.2

0.97.1

Patch Changes

  • Updated dependencies [dbaf72c]:
    • @graphql-mesh/types@0.97.1
    • @graphql-mesh/utils@0.97.1
    • @graphql-mesh/transport-soap@0.1.1

0.97.0

Patch Changes

  • Updated dependencies [92dce67, 70b05a2]:
    • @graphql-mesh/types@0.97.0
    • @graphql-mesh/utils@0.97.0
    • @graphql-mesh/transport-soap@0.1.0

0.96.7

Patch Changes

  • Updated dependencies [0f274ef]:
    • @graphql-mesh/utils@0.96.6
    • @graphql-mesh/types@0.96.6
    • @graphql-mesh/transport-soap@0.0.3

0.96.6

Patch Changes

  • Updated dependencies [4b3ea1d]:
    • @graphql-mesh/types@0.96.5
    • @graphql-mesh/transport-soap@0.0.2
    • @graphql-mesh/utils@0.96.5

0.96.5

Patch Changes

0.96.4

Patch Changes

0.96.3

Patch Changes

0.96.2

Patch Changes

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

0.96.1

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/types@0.96.1
    • @graphql-mesh/utils@0.96.1

0.96.0

Patch Changes

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

0.95.10

Patch Changes

  • Updated dependencies [b4d38c55d]:
    • @graphql-mesh/string-interpolation@0.5.3
    • @graphql-mesh/utils@0.95.8
    • @graphql-mesh/types@0.95.8

0.95.9

Patch Changes

0.95.8

Patch Changes

  • Updated dependencies [a13969c77]:
    • @graphql-mesh/types@0.95.7
    • @graphql-mesh/utils@0.95.7

0.95.7

Patch Changes

0.95.6

Patch Changes

  • Updated dependencies [8e1056cf9]:
    • @graphql-mesh/string-interpolation@0.5.2
    • @graphql-mesh/utils@0.95.6
    • @graphql-mesh/types@0.95.6

0.95.5

Patch Changes

  • Updated dependencies [b8f16a42b, b8f16a42b]:
    • @graphql-mesh/cross-helpers@0.4.1
    • @graphql-mesh/types@0.95.5
    • @graphql-mesh/utils@0.95.5

0.95.4

Patch Changes

  • Updated dependencies [625e5d787]:
    • @graphql-mesh/types@0.95.4
    • @graphql-mesh/utils@0.95.4

0.95.3

Patch Changes

  • Updated dependencies [33ae7a89a]:
    • @graphql-mesh/types@0.95.3
    • @graphql-mesh/utils@0.95.3

0.95.2

Patch Changes

  • Updated dependencies [d8da4b282]:
    • @graphql-mesh/types@0.95.2
    • @graphql-mesh/utils@0.95.2

0.95.1

Patch Changes

0.95.0

Patch Changes

  • Updated dependencies [bb50c4f94]:
    • @graphql-mesh/types@0.95.0
    • @graphql-mesh/utils@0.95.0

0.94.9

Patch Changes

  • Updated dependencies [d1310cdff]:
    • @graphql-mesh/utils@0.94.6
    • @graphql-mesh/types@0.94.6

0.94.8

Patch Changes

  • Updated dependencies [f11e9b307]:
    • @graphql-mesh/utils@0.94.5
    • @graphql-mesh/types@0.94.5

0.94.7

Patch Changes

0.94.6

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/utils@0.94.3
    • @graphql-mesh/types@0.94.3

0.94.5

Patch Changes

  • Updated dependencies [d0d4917f4]:
    • @graphql-mesh/types@0.94.2
    • @graphql-mesh/utils@0.94.2

0.94.4

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/types@0.94.1
    • @graphql-mesh/utils@0.94.1

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

0.93.1

Patch Changes

1.0.0

Patch Changes

0.4.23

Patch Changes

0.4.22

Patch Changes

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

  • Updated dependencies [c90eb5ac6]:

    • @graphql-mesh/types@0.91.12
    • @graphql-mesh/utils@0.43.20

0.4.21

Patch Changes

  • Updated dependencies [7e7096695]:
    • @graphql-mesh/types@0.91.11
    • @graphql-mesh/utils@0.43.19

0.4.20

Patch Changes

  • Updated dependencies [3f658a771]:
    • @graphql-mesh/utils@0.43.18
    • @graphql-mesh/types@0.91.10

0.4.19

Patch Changes

  • Updated dependencies [a272fdbca]:
    • @graphql-mesh/types@0.91.9
    • @graphql-mesh/utils@0.43.17

0.4.18

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/types@0.91.8
    • @graphql-mesh/utils@0.43.16

0.4.17

Patch Changes

0.4.16

Patch Changes

  • Updated dependencies [fa2c010c1]:
    • @graphql-mesh/utils@0.43.15
    • @graphql-mesh/types@0.91.7

0.4.15

Patch Changes

0.4.14

Patch Changes

  • Updated dependencies [5c19f8d6f]:
    • @graphql-mesh/types@0.91.5
    • @graphql-mesh/utils@0.43.13

0.4.13

Patch Changes

  • Updated dependencies [63ab17f0b]:
    • @graphql-mesh/types@0.91.4
    • @graphql-mesh/utils@0.43.12

0.4.12

Patch Changes

  • Updated dependencies [8c9c39cf5, 8c9c39cf5]:
    • @graphql-mesh/types@0.91.3
    • @graphql-mesh/utils@0.43.11

0.4.11

Patch Changes

  • Updated dependencies [989a47802]:
    • @graphql-mesh/types@0.91.2
    • @graphql-mesh/utils@0.43.10

0.4.10

Patch Changes

  • Updated dependencies [d694ccc1f]:
    • @graphql-mesh/utils@0.43.9
    • @graphql-mesh/types@0.91.1

0.4.9

Patch Changes

0.4.8

Patch Changes

0.4.7

Patch Changes

0.4.6

Patch Changes

0.4.5

Patch Changes

0.4.4

Patch Changes

0.4.3

Patch Changes

  • Updated dependencies [99f4c84e6, 99f4c84e6]:
    • @graphql-mesh/types@0.89.3
    • @graphql-mesh/utils@0.43.4

0.4.2

Patch Changes

  • Updated dependencies [deb9912e0]:
    • @graphql-mesh/types@0.89.2
    • @graphql-mesh/utils@0.43.3

0.4.1

Patch Changes

  • Updated dependencies [f1c2e20e5, f1c2e20e5]:
    • @graphql-mesh/types@0.89.1
    • @graphql-mesh/utils@0.43.2

0.4.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]:
    • @graphql-mesh/types@0.89.0
    • @graphql-mesh/utils@0.43.1

0.3.0

Minor Changes

Patch Changes

0.2.3

Patch Changes

  • Updated dependencies [eba73c626]:
    • @graphql-mesh/utils@0.42.9
    • @graphql-mesh/types@0.87.1

0.2.2

Patch Changes

  • Updated dependencies [0d9771428, 686b3301b]:
    • @graphql-mesh/types@0.87.0
    • @graphql-mesh/utils@0.42.8

0.2.1

Patch Changes

0.2.0

Minor Changes

  • c55e68381 Thanks @ardatan! - BREAKING - wsdl renamed to source so you should update your configuration file

Patch Changes

0.1.2

Patch Changes

0.1.1

Patch Changes

0.1.0

Minor Changes

  • #3137 672c62d50 Thanks @ardatan! - BREAKING Rewrite SOAP Handler

    The generated API is completely different now because of the new handler. The new handler is based on the new @omnigraph/soap package. The fields in the generated schema now follows the XML structure.

Patch Changes

  • Updated dependencies [d5f2d950e]:
    • @graphql-mesh/utils@0.42.4
    • @graphql-mesh/types@0.85.5