Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upcoming Release Changes #4217

Merged
merged 1 commit into from
Aug 4, 2022
Merged

Upcoming Release Changes #4217

merged 1 commit into from
Aug 4, 2022

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Aug 2, 2022

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.

Releases

@graphql-mesh/[email protected]

Minor Changes

  • 945f49887 Thanks @ascheffe-kenna! - Allow swagger docs that don't have defined schema refs. Right now whole app crashes if a schema is missing a \$ref;

      /**
       * Allow processing to continue if the swagger schema is missing a schema $ref.
       */
      allowUndefinedSchemaRefTags?: boolean;
    
      /**
       * Object type to use for missing swagger schemas refs default is object.
       */
      defaultUndefinedSchemaType?: 'string' | 'number' | 'object' | 'array' | 'boolean' | 'integer';

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

[email protected]

Patch Changes

  • #4221 12430d907 Thanks @ardatan! - Respect "required" field in anyOf and allOf schemas and fix the bug that puts an Any schema if this kind of schema is present

  • #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.

  • #4221 12430d907 Thanks @ardatan! - Use single "Any" schema for unknown types defined in "required" in order to prevent duplication

  • Updated dependencies [02c018249]:

@omnigraph/[email protected]

Patch Changes

  • 78552ab23 Thanks @ardatan! - Respect "nullable" property of a property schema

  • #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.

  • #4220 961e07113 Thanks @ardatan! - Delete the escaped field name in favor of unescaped/original field name to keep the expected structure

    For example if you have foo-bar in your request input, it is sanitized to foo_bar in order to fit the requirements of GraphQL specification. But then, JSON Schema loader recovers it to the original foo-bar field name before sending request. But it was sending both field names.

    input FooBar {
      foo_bar: String
    }

    Before;

    {
      "foo-bar": "baz",
      "foo_bar": "baz"
    }

    After;

    {
      "foo-bar": "baz"
    }
  • Updated dependencies [12430d907, 02c018249, f95036a33, 12430d907]:

@omnigraph/[email protected]

Patch Changes

@omnigraph/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

@graphql-mesh/[email protected]

Patch Changes

  • #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.

  • Updated dependencies []:

@graphql-mesh/[email protected]

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
  • Updated dependencies [f95036a33]:

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

@vercel
Copy link

vercel bot commented Aug 2, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated
graphql-mesh ✅ Ready (Inspect) Visit Preview Aug 4, 2022 at 2:28PM (UTC)

@github-actions github-actions bot force-pushed the changeset-release/master branch from dc2d090 to 222250f Compare August 3, 2022 08:47
@github-actions github-actions bot force-pushed the changeset-release/master branch 4 times, most recently from 2458db2 to e0eb97a Compare August 3, 2022 10:59
@github-actions github-actions bot force-pushed the changeset-release/master branch 2 times, most recently from e670046 to 9322dc7 Compare August 3, 2022 11:13
@github-actions github-actions bot force-pushed the changeset-release/master branch from 9322dc7 to a04b82a Compare August 3, 2022 11:41
@github-actions github-actions bot force-pushed the changeset-release/master branch from a04b82a to c6fa4b8 Compare August 3, 2022 13:57
@github-actions github-actions bot force-pushed the changeset-release/master branch from c6fa4b8 to 7aee049 Compare August 3, 2022 15:21
@github-actions github-actions bot force-pushed the changeset-release/master branch from 7aee049 to c7730c7 Compare August 3, 2022 16:29
@github-actions github-actions bot force-pushed the changeset-release/master branch from c7730c7 to a95ad2f Compare August 3, 2022 21:21
@github-actions github-actions bot force-pushed the changeset-release/master branch from a95ad2f to f7b0c9e Compare August 3, 2022 22:13
@github-actions github-actions bot force-pushed the changeset-release/master branch from f7b0c9e to 3765e2d Compare August 4, 2022 00:23
@github-actions github-actions bot force-pushed the changeset-release/master branch from 3765e2d to 93689b1 Compare August 4, 2022 06:03
@github-actions github-actions bot force-pushed the changeset-release/master branch from 93689b1 to 5cf6580 Compare August 4, 2022 06:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant