On this page

@graphql-mesh/string-interpolation

Changelog for @graphql-mesh/string-interpolation: every release with its changes and the pull requests behind them.

0.5.18

Patch Changes

0.5.17

Patch Changes

0.5.16

Patch Changes

  • 94fbfbd Thanks @ardatan! - When {missing} tries to interpolate missing key from the context, it returns undefined. If the entire string is just the placeholder, it should return undefined instead of the string with undefined in it. This change adds a check for this case and returns undefined when the entire string is a placeholder for an undefined value.

0.5.15

Patch Changes

0.5.14

Patch Changes

0.5.13

Patch Changes

  • #9347 13af2ff Thanks @ardatan! - If the entire interpolation string is a placeholder for a value, then return that value;

    If { args: { n: 1, flag: true, name: 'test' } } is passed as data,

    • {args} will return { n: 1, flag: true, name: 'test' }
    • {args.name} will return "test"
    • {args.n} will return 1
    • {args.flag} will return true

0.5.12

Patch Changes

0.5.11

Patch Changes

  • #9151 0028f3b Thanks @ardatan! - Return undefined when interpolated string is completely an expression that resolves to undefined

    stringInterpolator.parse('{missing}', {})

    will now return undefined instead of the string ''.

    Also if the given string is undefined, return an undefined too;

    stringInterpolator.parse(undefined, {})

    will return undefined instead of the string ''.

0.5.10

Patch Changes

0.5.9

Patch Changes

0.5.8

Patch Changes

  • #8301 78c202e Thanks @ardatan! - Avoid logging sensitive data directly. Instead, log a generic error message without including the potentially sensitive str variable. This way, it still notifies of errors without risking the exposure of sensitive information.
    • Replace the logging statement on line 176 in packages/string-interpolation/src/interpolator.js to avoid logging the str variable.
    • Ensure that the new logging statement provides enough information to debug the issue without exposing sensitive data.

0.5.7

Patch Changes

0.5.6

Patch Changes

0.5.5

Patch Changes

0.5.4

Patch Changes

0.5.3

Patch Changes

0.5.2

Patch Changes

0.5.1

Patch Changes

0.5.0

Minor Changes

Patch Changes

0.4.4

Patch Changes

0.4.3

Patch Changes

0.4.2

Patch Changes

0.4.1

Patch Changes

0.4.0

Minor Changes

Patch Changes

0.3.3

Patch Changes

0.3.2

Patch Changes

0.3.1

Patch Changes

0.3.0

Minor Changes

  • 13b9b30f7: Add interpolation strings to the generated MeshContext type

0.2.0

Minor Changes

  • 974e703e2: No longer import entire lodash library but instead individual smaller packages

Patch Changes

  • 974e703e2: Cleanup dependencies
  • 974e703e2: Use deeper lodash imports to have better treeshaking and avoid using eval

0.1.0

Minor Changes

  • 2e9addd80: Use platform agnostic json-pointer instead of json-ptr

Patch Changes

  • 2e9addd80: Bump cross-undici-fetch for Node 18 compat

0.0.1

Patch Changes

  • 7856f92d3: Bump all packages